March 13, 2014 at 12:06 am
Hi,
I have a rather simple, one would think, question.
Clustering sql, we have a active active node setup, whats the best way....
ClusterNode1\Instance1
ClusterNode2\Instance2
???
Then whats the best practice on NAMING those instances, Instance1? node1? Something more specific to the database name? We have SEVERAL databases in each instances, so something to the functional area perhaps?
The future is to move to 4 or 6 node combined fully active cluster with multiple instances.
One of our DBA's has had a heartattact trying to explain the concepts, and I think he needs a paramedic.
Anyone can assist would be greatly appreciated.
March 13, 2014 at 12:20 am
Naming should not be Node specific. Bcs in cluster nodes are always transparent.
It's better to have the name as department specific. Or if you have Application specific clusters it can me named as Application specific.
For instance, sharepoint cluster can be named something likeas CLUSHPTDB01\Instance1.
Naming should be something likethis ..
Node1 : SQLVirtualName\Instance1
Node2 : SQLVirtualName\Instance2
--
SQLBuddy
March 13, 2014 at 4:51 am
paul-1007285 (3/13/2014)
Hi,I have a rather simple, one would think, question.
Clustering sql, we have a active active node setup, whats the best way....
ClusterNode1\Instance1
ClusterNode2\Instance2
???
Then whats the best practice on NAMING those instances, Instance1? node1? Something more specific to the database name? We have SEVERAL databases in each instances, so something to the functional area perhaps?
The future is to move to 4 or 6 node combined fully active cluster with multiple instances.
One of our DBA's has had a heartattact trying to explain the concepts, and I think he needs a paramedic.
Anyone can assist would be greatly appreciated.
The node names are not used for a clustered instance, each new instance you install requires a new virtual computername or virtual networkname to give its correct name.
There is no BP for the VNNs, they must conform to Windows\AD rules for computername objects, generally 15 characters or less.
In a simple example we see
Cluster Node name IP address
Clusternode1 10.10.10.150
Clusternode2 10.10.10.151
Clusternode3 10.10.10.152
1st clustered instance SQLClust01\SPProd
VNN Instance name IP address
SQLClust01 SPProd 10.10.10.159
2nd clustered instance SQLClust02\DSProd
VNN Instance name IP address
SQLClust02 DSProd 10.10.10.160
Take a look through my guide on this site to get a better understanding how SQL Server failover clusters work.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply