Disk subsytem in clustering SQL server

[pie8ter]

Because clustering SQL 2005 server requires at least two nodes and a seperate storage (SAN) server, where do I put the transaction logs and database files to maximize performance.

Is it better to keep both transaction and database files in the SAN. I would guess both should be in the SAN as the DB file will be out of synch if the log is in the cluster nodes.

Where would the virtual IP and server name be hosted for the cluster? I am guessing it's not on either of the nodes.


Thanks

 

[mrdenny]

Both the data files and log files must be kept on the SAN. SQL will not allow you to place data files on a drive which the SQL Server cluster resource isn't dependant on, and you can not make a cluster resource dependant on a local drive.

The virtual IP and host name of the SQL Server will be what ever IP and hostname you enter during the SQL install.

The basic setup of a cluster will be something like this.
Physical Machines
SERVER1A - 192.168.0.2
SERVER1B - 192.168.0.3

When you setup the machines as a cluster (which must be done prior to setting up SQL) you setup a virtual name and an IP. In this case the virtual name is SERVER1 with an IP in the same subnet as the physical machines. In this case I'll use 192.168.0.4. This is the cluster root.

Now that the machines are clustered you can setup the rest of the clustered resources such as the data drives, log drives, etc. Add these into a seperate resource group from the cluster root.

When you install SQL you will need to give it a unique name and IP address specifically for the SQL server. In this case I'll use VIRTUAL1 with an IP of 192.168.0.5.

For each clustered instance of SQL that you install you will need a seperate hostname and IP address.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com