Article ID: 274446 - Last Review: April 18, 2006 - Revision: 5.2

Upgrade to SQL Server 2000 failover solution recommended for all non-SQL Server 2000 virtual servers

View products that this article applies to.
This article was previously published under Q274446
Expand all | Collapse all

SUMMARY

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:
243218  (http://support.microsoft.com/kb/243218/EN-US/ ) INF: Installation Order for SQL Server 2000 Enterprise Edition on Microsoft Cluster Server
With 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.

Similarly, the SQL Server 2000 utilities and administration tools have been enhanced to work with failover clusters. The administration tools include:
  • Full-Text Search/Queries

  • SQL Server Enterprise Manager

  • SQL Server Service Control Manager

  • SQL Server Profiler

  • SQL Server Query Analyzer
For more information about the functionality of these tools, refer to the following topics in SQL Server 2000 Books Online:
  • "Failover Clustering Support"

  • "Using SQL Server Tools with Failover Clustering"
Due to the improved functionality and recoverability with SQL Server 2000 cluster implementations, Microsoft recommends that companies upgrade all currently clustered SQL Server 6.5 and SQL Server 7.0 clustered servers to SQL Server 2000 as soon as possible. A SQL Server cluster upgrade may not be possible on computers that have legacy applications running as a production environment with the SQL Server cluster. If that is the case, please contact your application vendor for assistance or requirements to upgrade.

MORE INFORMATION

The issues and warnings discussed in the following Microsoft Knowledge Base articles no longer apply to SQL Server 2000 clustering:
254593  (http://support.microsoft.com/kb/254593/EN-US/ ) INF: Troubleshooting SQL Cluster Wizard Failures
247110  (http://support.microsoft.com/kb/247110/EN-US/ ) PRB: Replication Must be Removed Before Applying Service Pack
235987  (http://support.microsoft.com/kb/235987/EN-US/ ) Virtual SQL Server Only Supports One TCP/IP Address
225092  (http://support.microsoft.com/kb/225092/EN-US/ ) Evicting a Node in a Cluster Can Cause Problems in SQL 6.5 or 7.0
183959  (http://support.microsoft.com/kb/183959/EN-US/ ) PRB: SVS Can Not Run on Other Node After Node Rebuilt
313037  (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:
http://technet.microsoft.com/en-us/events/bb643137.aspx (http://technet.microsoft.com/en-us/events/bb643137.aspx)
APPLIES TO
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 6.5 Enterprise Edition
  • Microsoft SQL Server 7.0 Enterprise Edition
Back to the top
Keywords: 
kbbug kbclustering kbinfo KB274446
 

Get Help Now

Contact a support professional by E-mail, Online, or Phone

Article Translations

 

Related Support Centers