Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Naming convention advice for clustered servers

Status
Not open for further replies.

tom11011

MIS
Oct 12, 2001
537
US
Hi there,

I am embarking on my first sql clustering experience.

I wanted to get some advice on naming conventions for the servers. There are 2 in the cluster right now.

My feeling is that generally there can be more than one cluster group of servers and each group could have any number of nodes.

thanks for any advice.
 
If I understand correctly you are asking the naming conventions of cluster server.
The rule of thump is start with default instance then add
\VS2, VS3...., VS16 for SQL 2000 and I read that you can name some where upto 256 named instance 2K05. I might be wrong about it but you can go min 16.
Example:

MyProd is default instance
MyProd\VS2
MyProd\VS3
It's important to name all named instnaces in with \AnyName
Hope this helps


Dr.Sql
Good Luck.
 
Here is how we have ours setup

For the physical Servers we use:
SERVER1A
SERVER1B
SERVER1C
SERVER1D
We then create at least two Cluster groups.

The first is called SERVER1. It holds all the common resources such as DTC, the Q drive, the agents for the backup software, etc.

The second is called SERVER1V01. This is for the first virtual server on the cluster. It would hold an instance called SERVER1V01\OLTP?? or SERVER1V01\DSS?? (The named instance are required for our DR setup.

Each SQL Server get's it's own cluster group and it's own machine name. If I wanted a second instance on a machine the name is then SERVER1V02\OLTP??

We use a two digit identifier as we have decided that no cluster should have more than 16 virtual worlds on it so the two digit works for us.

Also all instance names are unique accross the enterprise. So there will only be one OLTP01 instance in the entire company. This give us greater flexability if we need to merge two clusters together or split a cluster apart into two clusters, etc. It is also for our DR setup.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top