This article has been archived. It is offered "as is" and will no longer be updated.
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:
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:
Open the Cluster Administrator.
Make sure that all the physical disk resources that contain SQL Server databases are in the same group as the SQL Server resource.
Right-click the SQL Server resource, and then bring the resource into an Offline state by clicking Bring Offline.
Right-click the SQL Server resource, and then click Properties.
Click the Dependencies tab.
Click Add to add the disk to the dependencies list for that resource.
Bring the SQL Server resource back online, and then add the SQL Server files on that shared cluster disk.
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:
Uncluster SQL Server 7.0.
Upgrade the stand-alone SQL Server 7.0 server to a default instance of SQL Server 2000.
Upgrade the default instance to a clustered instance.
Applying the service pack to the default instance and then upgrading to the clustered instance does not add the proper disk dependencies. To add the proper disk dependencies, you must install the service pack after the upgrade to the clustered instance.