ansaurus

Question

SQL Server Express 2008 using (local) in connection string

Answer 1

A:

You can use the SQL Server Configuration Manager tool to create an alias. Give the alias the same name on both your machine, and then you can just reference the alias in your configuration files.

I don't know if the Configuration Manager tool is actually included with the Express version of SQL Server, but if not then you can just use the registry key (it still works with Express editions). Just get your coworker to set up the alias and then export the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo

You can then import that key on your local computer. Things are slightly more complicated if you're on 64-bit Windows (because you have to set up the alias in both the 64-bit and 32-bit registry).

Dean Harding 2010-05-18 00:20:41

I am on a 64-bit machine. In SQL Server Configuration Manager I setup an Alias under both the 32-bit and 64-bit SQL Native Client 10.0 Configuration sections. Then using that alias as the server name in the connection string I get the following 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"

Jeff T 2010-05-18 00:38:00

So one more bit of info that I think is helping to cause me problems is that I have a full version of 2005 installed on the same machine. When I go to SSMS and connect to (local) it is taking me to the 2005 instance.I also just saw that when I go to the SQL Server Configuration Manager for my 2005 instance it also now has the Alias listed.I'm thinking that uninstalling 2005 might just solve my problems.

Jeff T 2010-05-18 00:50:52

Another tip about setting up the alias...if it's localhost, you can use "Named Pipes" for the protocol. That worked for me, whereas I couldn't get the TCP protocol to work, even after enabling the protocol.

Dan Tanner 2010-06-10 04:13:10

Answer 2

+1 A:

Assuming you both have SQL Express installed with the default instance name "SQLEXPRESS", you can have 1 connection string like:

server=.\SQLEXPRESS;integrated security=SSPI;database=DBNAME

The "." in the connection string is used to represent the local machine.

Wallace Breza 2010-05-18 13:57:52

I would post this as my answer but it looks like Wallace got here first.

Wardy 2010-05-18 14:26:00

ansaurus

tags:

views:

answers:

SQL Server Express 2008 using (local) in connection string

related questions