January 20, 2012 at 12:47 pm
I built three SQL Server clusters in similar fashion, but the following problem exists on the last cluster build.
Unable to register the named instance (which lives on Node B) on Node A using [VirtualServerNameamed instance]. The named instance will register on Node A using [VirtualServerName, port].
Here’s the cluster makeup:
Active-Active SQL Server 2008 R2 Cluster
Windows Server 2008 R2 Enterprise
VirtualServerName1 = Default InstanceVirtualServerName2 = Named Instance
Active on Node A Active on Node B
Server Registrations Server Registrations
VirtualServerName1 VirtualServerName2\NamedInstance
VirtualServerName2, port VirtualServerName1
I would like to register the named instance on Node A without using the port.
Thoughts?
January 20, 2012 at 2:03 pm
Is the SQL Server Browser service started?
January 26, 2012 at 12:29 am
couldnt understand your question exactly.
On Node A you have Default instance ( VirtualServername1) and Node B you have named instnace (VirtualServername2\instancename). You want to connect to Node B from Node A without using port number?
You should be able to do it when you specify VirtualServername2\instancename or Virtual IP that you would have created. Your SQL Virtual IPs for both installations should have been different.
Regards,
Raj
January 26, 2012 at 12:47 pm
The Browser service is started on both nodes.
January 26, 2012 at 12:50 pm
arr.nagaraj (1/26/2012)
couldnt understand your question exactly.On Node A you have Default instance ( VirtualServername1) and Node B you have named instnace (VirtualServername2\instancename). You want to connect to Node B from Node A without using port number?
You should be able to do it when you specify VirtualServername2\instancename or Virtual IP that you would have created. Your SQL Virtual IPs for both installations should have been different.
This issue is I'm unable to connect to the named instance "VirtualServername2\instancename" from Node A.
Please advise.
January 26, 2012 at 1:25 pm
spenn6367 (1/26/2012)
arr.nagaraj (1/26/2012)
couldnt understand your question exactly.On Node A you have Default instance ( VirtualServername1) and Node B you have named instnace (VirtualServername2\instancename). You want to connect to Node B from Node A without using port number?
You should be able to do it when you specify VirtualServername2\instancename or Virtual IP that you would have created. Your SQL Virtual IPs for both installations should have been different.
This issue is I'm unable to connect to the named instance "VirtualServername2\instancename" from Node A.
Please advise.
The SQL browser service needs to be running on ALL nodes. Also you cannot reference the named instance simply by the IP address, you MUST reference it by IP and Port.
CEWII
January 26, 2012 at 8:18 pm
Elliott Whitlow (1/26/2012)
spenn6367 (1/26/2012)
arr.nagaraj (1/26/2012)
couldnt understand your question exactly.On Node A you have Default instance ( VirtualServername1) and Node B you have named instnace (VirtualServername2\instancename). You want to connect to Node B from Node A without using port number?
You should be able to do it when you specify VirtualServername2\instancename or Virtual IP that you would have created. Your SQL Virtual IPs for both installations should have been different.
This issue is I'm unable to connect to the named instance "VirtualServername2\instancename" from Node A.
Please advise.
The SQL browser service needs to be running on ALL nodes. Also you cannot reference the named instance simply by the IP address, you MUST reference it by IP and Port.
CEWII
If there is no default instance running currently on the Node and if the IPs are different ( as in the case above ) you can connect using the IP alone to a named instance
Regards,
Raj
January 27, 2012 at 8:19 am
arr.nagaraj (1/26/2012)
If there is no default instance running currently on the Node and if the IPs are different ( as in the case above ) you can connect using the IP alone to a named instance
I have to disagree, I have never seen this happen in practice or when I just tried it. I have a cluster with all named instances, one per node, attempts to reference ONLY the IP address failed to connect, as expected. The tools don't know WHERE the SQL server is, they might be able to assume the IP but the port cant be guessed, and without the instance name I don't believe that the SQL Browser can resolve it either.
Also keep in mind the only thing that really defines a default instance is that it listens on port 1433. Other than that its pretty much the same.
CEWII
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply