SQL Server Post SQL Installation Checklist (Part 4 of 4)

By:   |   Comments   |   Related: 1 | 2 | 3 | 4 | > Clustering

This is the fourth and final checklist in the process - run through it just after completing a SQL Server installation in any environment.

SQL Clustering Post-Installation Checklist


Pass Fail
If antivirus software is installed, set filter to exclude all Sql extensions (data files, snapshots, logs, full text catalogs and indexes), Sql Server program files path, Sql logging/tracing paths
Appropriate SQL Server service pack and hotfixes applied
SQL 2005 - Client tools installed individually on cluster nodes (if desired)
SQL 2005 - SSIS service installed individually on cluster nodes (if desired)
SQL 2005 - SSIS properly installed, configured, etc. for cluster use (if desired)
All SQL Server resources online and configured
Static port number assigned to the instance, protocols configured
Additional disk resources configured as dependencies of the SQL Server resource and verified (fn_servershareddrives or sys.dm_io_cluster_shared_drives)
"Affect the Group" option set correctly for Sql Server 2005 and Analysis Services 2005 resources
Advanced Security (IPSec, Kerberos, or SSL) enabled if appropriate
Verify possible owners list for ALL resources contains appropriate nodes
Preferred owners configured for more than two nodes
Resource group failback policy set (if modifications necessary)
Resource parameters set (if modifications necessary)
Resource group thresholds set (if modifications necessary)
Verify the failover of the SQL Server virtual server to and from all nodes in the cluster
Verify all applications with the failover of the SQL Server virtual server
Appropriate services marked to Not Affect Group and/or removed from cluster control (FTS, Backup drives, etc.)
Verify node participation for the instance (fn_virtualservernodes)
Model database reconfigured appropriately
Enable advanced configuration options
Default data/log file paths reset
Configure tempdb
Maintenance database created and configured on instance
Set appropriate default DB Options on system, model, and existing user databases (using DatabaseOptions.sql script if available)
Security configured appropriately (lockdown script if available)
Default server options configured appropriately (using ServerOptions.sql script if available)
SQL Agent properties configured
Standard jobs, alerts, monitoring systems, procedures deployed to system
Capture MPS Reports (cluster, Sql, Setup/Perf) for each node in the cluster
If desired, installation account (ideally the Cluster Admin account) can have privilege to ADD ACCOUNTS to each of the Domain Groups for Sql Server-related accounts revoked (no longer required)
SqlIoSim run to baseline disk subsystem health and configuration
SqlIo run to baseline throughput limitations of IO system
Clear event logs (if desired) and archiv0065

sql server categories

sql server webinars

subscribe to mssqltips

sql server tutorials

sql server white papers

next tip

About the author
MSSQLTips author Chad Boyd Chad Boyd is an Architect, Administrator and Developer with technologies such as SQL Server, .NET, and Windows Server.

This author pledges the content of this article is based on professional experience and not AI generated.

View all my tips

Comments For This Article

get free sql tips
agree to terms