Prerequisites - Microsoft SQL Server 2005 failover cluster install

Microsoft SQL Server requires to communicate over a firewall. The default SQL Server port is 1433, and client ports are assigned a random value between 1024 and 5000

Clients accessing the server will need to be configured to use this port, and any firewall in between the client and the server will need to allow this traffic.

AD service account for the SQL Server service

The AD service account used to start the SQL Server service is NOT a member of the local administrator group. Applies to both installation of a SQL default instance or a SQL named instances.

The AD group is not required for a standalone installation but is mandatory for a cluster installation. For a standalone installation, the installation program will create a local group on the server to be used by SQL.


To read more about Active Directory Objects and Local Policies for Micorsoft Cluster Service and SQL Server failover cluster click here.

Enabling physical address extentions (PAE) and /3GB:

Follow the steps below:

Locate boot.ini file in the c:\ partition.

Remove Read-Only and Hidden attributes.

Execute at the command prompt: attrib –r –s –h c:\boot.ini

Open the Boot.ini file with the Notepad text editor. To add the /PAE /3GB parameters to the ARC path, add the /PAE and /3GB switches like in this example:

multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows 2003 Server Enterprise Edition" /PAE /3GB

On the File menu, click Save.

Restore the Read-Only attribute to the Boot.ini file.

Execute at the command prompt: C:\>attrib +r +s +h c:\boot.ini

The server needs to be restarted in order for the changes to take effect.

IMPORTANT: "/3GB" should not be used if the SQL Server machine has more than 16 GB of RAM

Confirm all the SQL LUN have been set to 64kb per cluster

This section describes the steps, required to format disks, used for SQL Server database data and log files.

SAN disks used for SQL data, log and backup partitions should be formatted with 64 KB per cluster and 64K offset.

Steps to do:

There must be no partition on the disk. If there is a partition, it needs to be deleted.

Virtual Disk Service: Enable the service, set it to Manual and start the service

Open a command prompt and type

Diskpart if windows 2003 or Diskpar is windows 2000

Type “Select disk number” where number is the actual number of the disk and press enter

Type “create partition primary align = 64” and press enter

If you receive a successful disk creation, continue

If a failure, proceed to the resolution section. The failure can occur on the cluster.

Close the Command prompt

Go to “Start>Programs>Administrative Tools” select “Computer Management” & Select “Disk Management”

Find the newly presented drive by identifying the disk number and size.

Right click and select format

In the format window: Set the “name” and set the “allocation unit size” to 64k

Do not select “perform a quick format”

Virtual Disk Service: Stop the service and set it to Disabled.

Latest Windows Service Pack Installed

Click here to read instructions on how to install Windows Server 2003 SP2.

MSDTC Cluster Configuration

MSDTC service needs to be configured ‘Network’. If it is a clustered installation, it also needs to be clustered. Click hereto read instructions on how to configure MSDTC for cluster configuration.

Cluster Only – Validation

Ensure both COM+ services are running on ALL nodes of the cluster

Check the cluster groups

• Validate the cluster name and IP address.
• Check if the SQL Virtual Name and IP address is in use.

Services

• Ensure MSDTC is clustered and running, it is required for a SQL cluster installation.
• Ensure the Task Scheduler service is running on all the nodes of the cluster.
• Ensure both COM+ services are running on ALL nodes of the cluster

All set? Go right ahead with MS SQL Server 2005 installation. All the best. Click here for video and instructions.