Prerequisites - Microsoft SQL Server 2008 failover cluster install
1. Server in domain
- Verify that server is part of the domain.
- If cluster, validate that virtual names and IPs are not in use (for cluster, MSDTC and SQL instance)
- Verify OS version and Service Pack level. Eg: For SQL Server 2008 installation on Windows Server 2003, SP2 is required
- Check hostname on each node.
- At a command prompt, type: hostname
- Ensure partitions used by SQL Server are created with offset=64k and formatted using 64K block size.
- Check drive letter assignments.
- Correct assignments for each node.
- Correct size for each drive.
- Validate all disk resources to be used by SQL instance have been added to the cluster.
- SQL installation needs to be executed from the node owning the cluster resources.
- For cluster installation, use mount points to minimize a number of drive letters required.
- For a standalone installation, using drive letters is fine unless there will be an issue with too many drive letters to use in which case, you have to use mount points.
- Set the right permissions on the drives to be mounted. The permissions should be (Full Control):
If cluster
- Check NIC setup: Refer to MSCS installation guide for more information.
- Ping each node of the cluster using the Public and Private networks.
- Repeat on each server.
- Ensure MSDTC Network access is configured. For MSDTC configuration click here
Note: “Enable SNA LU 6.2 Transactions” (Property in blue) is valid for Windows Server 2008 R2 only.
If Standalone
- Ensure Distributed Transaction Coordinator service is enabled and running.
- Ensure Task Scheduler service is running.
- Ensure both COM+ services are running.
- Ensure MSDTC is clustered.
- Ensure Task Scheduler service is running on all the nodes of the cluster.
- Ensure both COM+ services are running on ALL nodes of the cluster.
- The AD group is not required for a standalone installation but is mandatory for a cluster installation.
For standalone installation:
- The installation program will create a local group on the server to be used by SQL. The created local group must be added to the security policy settings that are pushed through GPO.
- The required local policies will be granted automatically by the setup program to the AD group during the installation. See Appendix “Local Policies (GPO)” for more information.
- Domain Security Groups for SQL Services and SQL DBA's must be created
- Created local group must be added to the security policy settings that are pushed through GPO.
Local Policies:
- ‘Perform volume maintenance’ policy will be set by GPO from OU level:
- Standalone: Add the SQL Group created during the SQL installation.
- Clustered: Add the AD ‘SQL Service’. This policy is required to enable the use of “Instant File Initialization” feature.
1. For Cluster Installation: The computer account for the SQL Virtual Name MUST BE created in proper OU before attempting the installation and DISABLED.
If the computer account for the SQL Virtual Name is not created or not disabled– installation will FAIL! It will be required to uninstall all the components and perform clean install.
2. (New for 2008) The SQL 2008 installation creates the SQL Name cluster resource with Kerberos authentication enabled. If the computer account is not created in AD prior to installation, the setup will fail.
3. The AD group for the SQL instance & AD service account(s) for the SQL instance are NOT a member of the Local administrators group
10. Windows Locale Setting
- Confirm Windows Locale Setting – use Control Panel.
- Regional and Language Options,
- Standards and formats= English (United States)
- Location = Canada
With the Windows Locale setting as above, a default SQL install will require SQL collation as: SQL_Latin1_General_CP1_CI_AS.
11. User Account running setup
Ensure user account running setup has following privileges:
- Bypass Traverse Checking
- Debug Programs
12. .Net Framework 3.5 SP1
Windows Server 2008 R2 has .Net Framework 3.5.1 as a component of OS. There is no installation required, but .Net Framework 3.5.1 needs to be enabled on Windows Server 2008 R2
13. Windows Installer 4.5
SQL 2008 requires Windows Installer version 4.5.
Windows Server 2008 and Windows Server 2008 R2 already have Windows Installer 4.5 version as part of the OS.
14. Windows Hotfix KB937444 – For Clustered Installations Only
This is applicable to Windows Server 2003.
Refer: http://support.microsoft.com/kb/937444
This is required for creation of File Shared cluster resources. The FileStream component of SQL server requires the hotifix even if FileStream is not selected or enabled during the installation. Hotfix should be applied to each node of the server.
15. SQL Server uses TCP port 1433 by default. For security reasons, it is highly recommended to change the TCP port immediately after SQL Server installation. Clients accessing the server will need to be configured to use that port, and any firewall in between the client and the server will need to allow traffic.
It is essential to set the stage for MS SQL Server 2008 installation and the prerequisites mentioned above will certainly help you get going. With all requirements in place, installation of MS SQL Server 2008 failover cluster is just a breeze. All the best. Click here for video and instructions.