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:
I think part of the problem is that
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?
answered Jun 24, 2010 at 11:02 AM
Kev Riley ♦♦
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].
So why not try disabling Shared Memory, then your aliasing tricks might have a chance?
answered Jun 25, 2010 at 08:15 AM
Kev Riley ♦♦