?
Solved

Unable to connect to the clustered SQL DB instance ?

Posted on 2012-04-10
3
Medium Priority
?
788 Views
Last Modified: 2012-04-11
Hi People,

I’ve created SQL Server 2008 R2 SP1 clustered virtual instance on top of my Windows Server 2008 R2 SP1 Enterprise MSCS, one instance is working fine and I can perform:

 
C:\telnet SQLClustername-instance1 1433

Open in new window

--> successfully

However with the other instance I cannot perform the above command and it is not accessible at all ? pinging the SQLClustername-instance2 is fine and reply back, when I do the following command:

C:\netstat –ano | find /I “1433”

Open in new window

 --> I cannot see the SQLClustername-instance2 IP address with port 1433 listening ?

I believe that the MSCS cluster can supports multiple SQL DB instance as long as the IP address is unique therefore port 1433 can be opened multiple times.

Any assistance would be greatly appreciated.

Thanks.
0
Comment
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 8

Author Comment

by:Senior IT System Engineer
ID: 37830323
Hi, so in this case there can be only one instance listening on port 1433 ?
From the SQL configuration manager, the instance2 ip address it is set 0 as dynamic port.

My BiztalkServer 2010 cannot somehow talk to this instance2?
So should I make it explicitly 1433 instead of 0?
0
 
LVL 8

Accepted Solution

by:
Senior IT System Engineer earned 0 total points
ID: 37831880
I've found the official way to do this finally from: http://msdn.microsoft.com/en-us/library/ms177440.aspx
0
 
LVL 28

Expert Comment

by:Ryan McCauley
ID: 37832796
You don't have to configure for a specific port - you can use the instance name, like "SERVER1\INSTANCENAME" (or "INSTANCEDNSNAME\INSTANCENAME", in the case of your clustered instance), or you can use the port number like "SERVER1,1440" (or whatever port you assigned). By default, ports are assigned dynamically every time the SQL engine starts up, and  assigning a port explicitly to your SQL Instance can cause problems if another application tries to grab that port on start-up.

With clustered instances, since you have a unique network name and IP address assigned to them, I've never understood why you need to specify the instance name in the connection - with a standard mutli-instance server, there are potentially two dozen instances listening on the same IP address, but with a cluster, each instance has its own IP. Connecting to "INSTANCEDNSNAME" has no confusion to it, and there should be no need to specify the instance name. To that point, I modify the TCP listener settings to allow this type of connection:

http://trycatchfinally.net/2009/05/accessing-a-clustered-sql-server-instance-without-the-instance-name/

Essentially, you tell SQL Server to listen on port 1433 of the cluster instance IP address, so requests to the IP directly (with no instance name) will still connect. Makes life a bit easier :)
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

719 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question