Article ID: 274446 - View products that this article applies to.
This article was previously published under Q274446
The administration of failover clusters has been improved so that a Microsoft SQL Server 2000 failover cluster is easy to install, configure, and maintain. The improvements in setup, maintenance, and disaster recoverability are substantial.
For additional information about SQL Server 2000 installations, click the article number below to view the article in the Microsoft Knowledge Base:
243218With SQL Server 2000 clustering, there are tremendous gains in recoverability. Through the SQL Server 2000 setup, you are given the ability to add or remove a node as a virtual SQL Server owner, and the ability to reinstall or rebuild a clustered instance on any node in the cluster without affecting the other clustered SQL Server instances.
(http://support.microsoft.com/kb/243218/EN-US/ )INF: Installation Order for SQL Server 2000 Enterprise Edition on Microsoft Cluster Server
Similarly, the SQL Server 2000 utilities and administration tools have been enhanced to work with failover clusters. The administration tools include:
The issues and warnings discussed in the following Microsoft Knowledge Base articles no longer apply to SQL Server 2000 clustering:
(http://support.microsoft.com/kb/254593/EN-US/ )INF: Troubleshooting SQL Cluster Wizard Failures
(http://support.microsoft.com/kb/247110/EN-US/ )PRB: Replication Must be Removed Before Applying Service Pack
(http://support.microsoft.com/kb/235987/EN-US/ )Virtual SQL Server Only Supports One TCP/IP Address
(http://support.microsoft.com/kb/225092/EN-US/ )Evicting a Node in a Cluster Can Cause Problems in SQL 6.5 or 7.0
(http://support.microsoft.com/kb/183959/EN-US/ )PRB: SVS Can Not Run on Other Node After Node Rebuilt
(http://support.microsoft.com/kb/313037/ )INF: Upgrading SQL Server Clusters to Windows Server 2003
For additional information about the benefits of upgrading, visit the following Microsoft Web site: