February 28, 2008 at 5:56 am
Generally I install SQL 2005 using the Default Instance Name. When asked for the SQL server (setting up the ODBC connection) I simply enter the name of the server.
I now have installed a new SQL 2005 server, and I gave it a unique Instance Name.
When asked for the SQL server (setting up the ODBC connection) what name do I enter? I assume it has to be more than the server name as the SQL server is unique. What format do I use to enter the unique name of the SQL db?
Any help appreciated.
Thanks,
Kerry
February 28, 2008 at 6:08 am
Hi,
You will need to use servername\instance name to connect (e.g. MyServer\MyInstance).
Cheers,
Phillip Cox
MCITP - Database Administrator
February 28, 2008 at 6:13 am
Phillip Cox (2/28/2008)
Hi,You will need to use servername\instance name to connect (e.g. MyServer\MyInstance).
That's exactly what I entered and it returns a failed to connect error??
February 28, 2008 at 6:23 am
Verify that you've got the names correct. Can you connect using management studio from a different machine?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 28, 2008 at 7:06 am
Grant Fritchey (2/28/2008)
Verify that you've got the names correct. Can you connect using management studio from a different machine?
I logged into the server itself, and noted the name [liuspc01\spc01] and used SQL Authentication and I get in fine.
February 28, 2008 at 7:13 am
Yeah, but did you log in from a different machine to the server? The reason is, you need to confirm that it's allowing external connections.
ODBC works fine with instance names. I just did a full test. It's got to be either your settings or the server configuration isn't allowing connections over the right protocols. Make sure your database has TCP/IP (assuming that's your network protocol) enabled in the SQL Server Configuration Manager.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 28, 2008 at 7:19 am
Grant Fritchey (2/28/2008)
Yeah, but did you log in from a different machine to the server? The reason is, you need to confirm that it's allowing external connections.ODBC works fine with instance names. I just did a full test. It's got to be either your settings or the server configuration isn't allowing connections over the right protocols. Make sure your database has TCP/IP (assuming that's your network protocol) enabled in the SQL Server Configuration Manager.
I think that is the problem. I just right clicked (selected Properties) on the DB and it returned the following error message:
An error occurred while establishing a connection to the server. When connectibg to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Any ideas?
:crazy:
February 28, 2008 at 7:31 am
You've checked Surface Area config on the new instance?
"Got no time for the jibba jabba!"
-B.A. Baracus
February 28, 2008 at 7:34 am
What ahutchens says and check the configuration manager.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply