FOR SQL SERVER 2000:
Case 1: If the default instance of sql server is to be upgraded to default clustered instance of sql server 2000
1) Only Default instance can be upgraded by this method
2) This Functionality is not vailable in sql server 2005 so if you want to convert a standalone instance of sql server 2005 into clustered we need to follow the steps mentioned in case 2 or case 3.
1) The Standalone instance of the sql server which is to be upgraded to cluster must have all it’s database with data and log files on the shared disk so that these files can be accessed by node 2 when the cluster fails over to node 2
2) The Sql server service must be running under the domain user account which has local administrator priviledges on both the nodes. This is a pre-requisite for a clustered instance of sql server.
Only after fulfilling the above pre-requisites we can go ahead with the steps mentioned below or else the “upgrade the existing instance to cluster” option in the wizard will be grayed and will not be activated.
1) On the Welcome screen of the SQL Server Installation Wizard, click Next.
2) On the Computer Name screen, click Local Computer. The computer you want to change from a default to a clustered instance should be displayed. You must be on the local computer to upgrade from a default to a clustered instance. Click Next.
3) On the Installation Selection screen, click Upgrade, remove, or add components to an existing instance of SQL Server. Click Next.
4) On the Existing Installation screen, click Upgrade your existing installation to a clustered installation. Click Next.
5) On the Virtual Server Name screen, enter a name for your virtual server. Click Next.
6) On the Failover Clustering screen, enter one IP address for each network configured for client access. That is, enter one IP address for each network on which the virtual server will be available to clients on a public (or mixed) network. Select the network for which you want to enter an IP address, and then enter the IP address. Click Add.
The IP address and the subnet are displayed. The subnet is supplied by Microsoft Cluster Service (MSCS). Continue to enter IP addresses for each installed network until you have populated all desired networks with an IP address. Click Next.
7 On the Cluster Management screen, review the failover cluster definition provided by SQL Server 2000. By default, all available nodes are selected. Remove any nodes that will not be part of the failover cluster definition for the virtual server you are creating. Click Next.
8 On the Remote Information screen, enter login credentials for the remote cluster node. The login credentials must have administrator privileges on the remote node(s) of the cluster. Click Next.
9 On the Services Accounts screen, select the service account(s) for the SQL Server services under which you want the failover cluster to run. Click Next.
10 On the Setup Complete screen, click Finish. If you need to restart the remote nodes in the failover cluster, you will be instructed to do so in the Setup Complete screen.
Case 2: If the default instance of sql server is to be upgraded to named clustered instance of sql server 2000
1. Install a clustered named instance of Microsoft® SQL Server™ 2000.
2. Run the Copy Database Wizard (CDW.exe) to move all databases and related information into the clustered, named instance of SQL Server 2000.
Optionally we can,
a. Take backup of all the system databases and user databases
b. Uninstall the default instance of sql server
c. Install a new clustered named instance
d. Restore the backup on this clustered instance
Case 3: If the Named instance of sql server is to be upgraded to Named clustered instance of sql server 2000
1) Take backup of all the system databases and user databases
2) Uninstall the default instance of sql server
3) Install a new clustered named instance with the same name
4) Restore the backup on this clustered instance