How To

How to upgrade from a SQL Server 7.0 active/active failover cluster (Setup)

Note  To upgrade from a Microsoft® SQL Server™ version 7.0 active/active failover cluster (or any configuration where SQL Server exists on the second node), you must first convert one side of the failover cluster to a named instance of SQL Server 2000.

To upgrade from a SQL Server 7.0 active/active failover cluster

  1. On Node 1, uncluster SQL Server version 7.0. Reboot Node 1.

  2. On Node 2, uncluster SQL Server 7.0. Reboot Node 2.

  3. On Node 1, install a clustered, named instance of SQL Server 2000 as a virtual server. This is not an upgrade process, but a side-by-side installation of SQL Server 7.0 and SQL Server 2000. Do not install the data to the same location/disk as Node 2. If you do, when you attempt to upgrade Node 2 from a SQL Server 7.0 to a SQL Server 2000 installation, Setup will fail.

  4. On Node 1, run the Copy Database Wizard (CDW.exe) to move all databases and related information from the SQL Server 7.0 installation into the clustered, named instance of SQL Server 2000. For more information about the Copy Database Wizard, see Using the Copy Database Wizard or How to upgrade databases online using the Copy Database Wizard (Enterprise Manager).

  5. On Node 1, uninstall SQL Server 7.0.

  6. On Node 2, upgrade SQL Server 7.0 to SQL Server 2000 as the default instance.

    You must install the binaries to a local drive and use a cluster disk for the data. This local drive is a path, which is a non-clustered disk valid on all nodes of the cluster. This drive on all nodes of the cluster must have at least 300 megabytes (MB) of available space.

  7. On Node 2, upgrade the default instance of SQL Server 2000 to a clustered instance.

    For more information, see How to upgrade from a default instance to a default clustered instance of SQL Server 2000 (SQL Server Setup).

Note  Optionally, you could create two named instances of SQL Server 2000 and use the Copy Database Wizard to upgrade both SQL Server 7.0 installations to a clustered, named instance of SQL Server 2000. This will provide better consistency, because all references to clustered installations of SQL Server 2000 will be in the form VirtualServer\Instance, rather than sometimes being just the servername, and sometimes both the servername and instancename.