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
|
Activity |
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 |
|
|
About Chad Boyd
Chad is an Architect, Administrator, and Developer with technologies such as Sql Server (and all related technologies), Windows Server, and Windows Clustering. He currently works as an independent consultant and also spends a significant amount of time writing, talking, presenting and blogging about Sql Server in person and online at http://mssqltips.com. In the past, Chad has worked with companies and organizations such as Microsoft Corporation and The American Red Cross, and provided consulting/support services at companies such as Bank of America, HP, Citigroup, Qualcomm, Scottrade, TJX, SunTrust, and Zurich Financial Services. For over 3 years with Microsoft Corporation Chad was responsible for providing onsite and remote support, guidance, and advice with SQL Server products to some of Microsoft’s foremost enterprise customers running the largest, most complex SQL Server installations and configurations in the world. This included all SQL Server products and versions, including SQL Server 7.0, 2000, 2005, and recently 2008, the SQL Server database engine, Reporting Services, SSIS/DTS, Notification Services, and Analysis Services on both 32 and 64 bit systems. Chad's primary responsibilities today include troubleshooting critical server situations, performance tuning and monitoring, disaster recovery planning and execution, architectural guidance for new Sql Server related deployments, and delivering deep technical workshops/presentations/proof-of-concept sessions covering a variety of technologies and functionality. Chad regularly posts Sql Server related content, tools, and advice with the mssqltips team at http://blogs.mssqltips.com/blogs and http://mssqltips.com. Chad can be contacted via his blog or email at chad dot boyd dot tips at gmail dot com.
