"Clustering" has become one of the biggest buzz words since SQL Server 2000 and Windows 2000 were introduced due to the improved manageability and reliability. Clustering in SQL Server 2000 is when two or more servers are configured to operate as a single virtual SQL Server to support database transactions. Each node or server in the cluster has the needed files installed locally as well as via a shared disk subsystem to support the SQL Server databases. A heart beat is used between the nodes to ensure each node is functioning properly, if not a failover occurs. Clustering is used to achieve high availability with SQL Server to support 24x7 operations to prevent a hardware failure from stopping an application from servicing client needs.
In a nutshell, with Windows 2000 Advanced Server and Windows 2003, two to 32 nodes can support a cluster to meet business needs. The two primary clustering modes for a two node cluster are:
- ActiveActive – Both nodes in the cluster process database transactions typically at 50% of the total resources because either node can fail-over to the other so that a single node would be responsible for the transactions of both nodes.
- ActivePassive – One node in the cluster processes database transactions and the second node processes database transactions only if the first node fails.
For additional information about clustering visit:
- SQL Server 2000 failover clustering
- Chapter 12 - Failover clustering
- An Introduction to SQL Server clustering
- SQL Server clustering and log shipping articles
For More Information
- Dozens more answers to tough SQL Server questions from Greg Robidoux and Jeremy Kadlec are available here.
- The Best Microsoft SQL Server Web Links: tips, tutorials, scripts, and more.
- Have a SQL Server tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical SQL Server questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, SQL Server, DB2, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
This was first published in May 2004