Article ID: 303119 - View products that this article applies to.
This article was previously published under Q303119
BUG #: 351023 (SHILOH_BUGS)
When you upgrade from a Microsoft SQL Server 7.0 cluster to a SQL Server 2000 clustered instance all the physical disk resources that contain SQL Server databases to the dependency list of the SQL Server resources are not added. Only the disk resource on which the master database resides is added to the dependency list. Disks that are not dependent upon the SQL Server resource may be taken offline without having to stop SQL Server, which may lead to data corruption.
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/290211/ )How to obtain the latest SQL Server 2000 service pack
To work around this behavior, manually add the physical disk resources that contain SQL Server databases to the SQL Server resource dependency list after the upgrade completes. To add the physical disk resources, follow these steps:
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
The SQL Server 2000 Service Pack 1 setup automatically adds all the physical disk resources that contain SQL Server databases to the SQL Server resources dependency list.
You can find the instructions for upgrading from a SQL Server 7.0 cluster to a SQL Server 2000 clustered instance in SQL Server 2000 Books Online; however, the general process is:
Article ID: 303119 - Last Review: March 15, 2006 - Revision: 3.3
Contact us for more help