Answered by:
Alias for SQL Server named instance

Question
-
I have SQL Server 2000 and SQLServer 2005 on my machine. The SQL Server 2005 has a named instance. From the server in Management Studio, I can load, and interact with both instances.
I have created an alias for the named instance. Now if I try to use the alias to connect in my Management studio, I am unable to do so.
I get an error saying " Cannot connect to sql2005InstanceAlias"
It says could not connnet because of the default setting does not allow for remote connections.
But, I have enabled remote connections.
I'm not sure what else do I have to do to use this alias?
Another question I had is after creating the alias on my machine, can someone else connect to the instance(the alias) without specifying the port number remotely and with the SQL browser running?
ThanksMonday, March 23, 2009 5:30 PM
Answers
-
Hello Seema
When you create an alias, it is specific to your client (PC)
So the answer is No, other PCs cannot use that alias without it being set up explicitly on their PCs
Regards
EwanTuesday, April 28, 2009 11:40 AM
All replies
-
The error that I get is:
TITLE: Connect to Server
------------------------------Cannot connect to sql2005InstanceAlias.
------------------------------
ADDITIONAL INFORMATION:An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
------------------------------
BUTTONS:OK
------------------------------Monday, March 23, 2009 6:17 PM -
Step 1) Make sure SQL SERVER is up and the instance you try to connect is running.
Step 2) Your system Firewall should not block SQL Server port.
Step 3) Go to Computer Management >> Service and Application >> SQL Server 2005 Configuration >> Network Configuration
Enable TCP/IP protocol. Make sure that SQL SERVER port is by Default 1433.
Step 4) Now follow this KB Article of MSDN depending on your server : http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
http://blog.sqlauthority.com/2007/04/23/sql-server-fix-error-40-could-not-open-a-connection-to-sql-server/
http://blog.sqlauthority.com/2008/08/09/sql-server-fix-error-1326-cannot-connect-to-database-server-error-40-could-not-open-a-connection-to-sql-server/
Regards,
Pinal Dave
Founder - http://blog.sqlauthority.com- Proposed as answer by Pinal Dave Saturday, April 4, 2009 7:08 AM
Saturday, April 4, 2009 7:07 AM -
Thanks. I was able to create an Alias for the named instance listening on a different port (not 1433) using my local SQL Server 2005 Management studio. Another question I had is after creating the alias on my machine, can someone else connect to the instance(the alias) without specifying the port number remotely and with the SQL browser running?
Regards, Seema- Edited by seemap123 Saturday, April 4, 2009 6:35 PM typo error
Saturday, April 4, 2009 6:33 PM -
Hello Seema
When you create an alias, it is specific to your client (PC)
So the answer is No, other PCs cannot use that alias without it being set up explicitly on their PCs
Regards
EwanTuesday, April 28, 2009 11:40 AM -
Thanks, Ewan.Tuesday, April 28, 2009 6:01 PM
-
Hello Seema
Please mark the reply that answered yor question if you're happy with the answer. It helps others who experience the same issue in future to find the solution.
Regards
EwanThursday, April 30, 2009 2:59 PM