Windows Failover Clustering can keep your SQL Server databases online and your customers happy when hardware or operating system problems strike. Failover Clustering also makes your life easier when you need to do maintenance on a physical server: just fail your SQL Server instance over to another server and complete your work with minimal downtime. However, be careful: If you misconfigure your cluster, then you are bound for poor SQL Server performance or extended unplanned downtime. You should not let an otherwise great high availability feature cause weak performance or outages. Let us learn how to avoid some of the most prevalent SQL Server cluster setup mistakes.
Read the 16-page whitepaper “Top Five SQL Server Cluster Setup Mistakes” by Kendra Little to learn about the top five mistakes that you can make for SQL Server Failover Clusters. It discusses: (1) Not planning your nodes and instances. (2) Buying the wrong hardware. (3) Selecting the wrong version of Windows or SQL Server. (4) Configuring quorum badly. (5) Skipping cluster validation (or ignoring warnings).
The presenter, Kendra Little, has been working with SQL Server for more than ten years. She has performance-tuned databases ranging from 1 gigabyte to 80 terabytes. Kendra is also a Microsoft Certified Master in SQL Server.