Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 SQL Server Administration (2008)
 Connection in Cluster

Author  Topic 

Leecau
Starting Member

5 Posts

Posted - 2010-05-06 : 06:05:48
Had a strange change to the way I connect to SQL Server and think it may be causing other issues for me.

I use to have to connect to each instance with ServerName/InstanceName
EG: SQLUAT1/SQLUAT1

Now suddenly I can only connect with the Instance name so only connecting with SQLUAT1 works - if I try SQLUAT1/SQLUAT1 it times out and is unable to connect.

Does anyone know how this can be caused to change and a way that I can connect using both options so nothing else breaks.

Thanks

Leecau
Starting Member

5 Posts

Posted - 2010-05-06 : 09:04:45
More information:
I did this (in reverse) from (http://www.trycatchfinally.net/blog-trycatchfinally/post/2009/05/06/Accessing-a-clustered-SQL-Server-instance-without-the-instance-name.aspx)
1. On the active node for the instance you're adjusting, open the "SQL Server Configuration Manager" from the start menu.
2. Expand "SQL Server Network Configuration" and select the instance you want to edit.
5. On the "IP Addresses" tab, scroll all the way to the bottom, to the "IPAll" section.
6. The "TCP port" box was set to 1433, the default port for SQL Server - I removed it to make it blank (the default setting here)
7. Restart the SQL Service on that node.

And now I connect via server/instance as I wanted however I can no longer connect via instancename itself. I need to do both as the applications have now been setup with using just instancename... but DBmail doesn't seem to work having it set that way.... any suggestions?
Go to Top of Page

vmenon
Starting Member

17 Posts

Posted - 2010-05-14 : 01:09:31
Let me summarize, currently you are able to connect via server\instance. You also want to achieve connection using only instancename.

The best way forward is "NOT" to make any further configuration changes, though I would prefer a SQL instance [if single on a node] to be on the default port or if there are multiple instances on a node, then each SQL instance be configured to listen on a static port.

On the client node(s) where the application is deployed, you can create an alias. The alias name will be the instancename and the server name for the alias will be server\instance. The application will then be able to successfully connect to the SQL instance by using just the instancename.

For more information do look up the article "How to: Create a Server Alias for Use by a Client" http://msdn.microsoft.com/en-us/library/ms190445.aspx
Go to Top of Page
   

- Advertisement -