SQL 2005 & 2008 R2 together on dev PC
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)
I've tried:
- 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 (local), localhost and . 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?
Assuming your machine is called MACHINE, and that the SQL instance MACHINE was the 2005 default instance, and now you have another instance called MACHINE\SQL2008R2, (I'm getting there....) can you not create an alias of MACHINE\SQL2008R2 called MACHINE?
Nice try, Kev, I hadn't thought of that. Sadly, that doesn't work either.
Another answer, as this is a different approach.....
You seem to be one the right track about shared memory
Connections to Microsoft SQL Server from a client running on the same computer use the shared memory protocol. Shared memory has no configurable properties. Shared memory is always tried first, and cannot be moved from the top position of the Enabled Protocols list in the Client Protocols Properties list. The Shared Memory protocol can be disabled, which is useful when troubleshooting one of the other protocols.
You cannot create an alias using the shared memory protocol, but if shared memory is enabled, then connecting to the Database Engine by name, creates a shared memory connection. A shared memory connection string uses the format lpc:[\instancename].
...
...
The word localhost or a period (.) can be used in place of (local).
So why not try disabling Shared Memory, then your aliasing tricks might have a chance?
Thanks, Kev. Sorry, I only just noticed you'd come back on this one! Another nice idea but still no luck. I think I'm going to just uninstal R2 and upgrade my 2005 instance in place instead. It's not a big deal now that I'm no longer finding any reason to use my 2005 instance or tools.
