I've installed 2008 R2 on my dev machine and now I want to get the R2 instance answering to the name (local). (I'm just not ready to uninstall 2005 yet just in case but quite a bit of our stuff uses (local) in the connection string for development purposes.) The SQL Browser service is running but connections to (local) aren't succeeding.
I keep getting this error:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
- Stopped all the 2005 services.
- Set up an alias in R2 called (local) that points to my R2 instance - with and without the port number the instance is listening on.
- Set up an alias called in R2 that redirects to the R2 instance and another called (local) that redirects to .
- Started the 2005 service and set up an alias called (local) that redirects to the R2 instance.
I think part of the problem is that
. are special server names that trigger the SQL Client to connect via the Shared Memory protocol. Aliases only cover the TCP/IP, Named Pipes and VIA protocols. I suspect that Shared Memory doesn't do aliasing, but I'm hoping there's some way to con it.
Any ideas, please?