You can convert from a standalone to MSCS SQL server clustered resource, if you like. In SQL Books Online, look for the article entitled "upgrading to default clustered instance". (These instructions assume that you have already installed/configured your MSCS basic clustering and have the shared physical disk resources, ip addresses, etc. set up.) Copied and pasted here for your convenience: How to upgrade from a default instance to a default clustered instance of SQL Server 2000 (Setup) Note This upgrade is from a default instance (a local installation where the data is on a local disk) to a clustered instance of Microsoft(r) SQL Server(tm) 2000. Use this upgrade step if you want to have a default virtual server. To upgrade from a default instance to a default clustered instance of SQL Server 2000 On the Welcome screen of the SQL Server Installation Wizard, click Next. 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. On the Installation Selection screen, click Upgrade, remove, or add components to an existing instance of SQL Server. Click Next. On the Existing Installation screen, click Upgrade your existing installation to a clustered installation. Click Next. On the Virtual Server Name screen, enter a name for your virtual server. Click Next. 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. 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. 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. 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. 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. -- Henry Sieff Network Engineer ph. 504-620-3420 mob. 504-931-4638 > -----Original Message----- > From: thin-bounce@xxxxxxxxxxxxx > [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Evan Mann > Sent: Friday, August 19, 2005 10:41 AM > To: thin@xxxxxxxxxxxxx > Subject: [THIN] OT: MSCS again > > If I want to take 3 existing SQL 2000 Server's and cluster > them with MSCS, is it going to require me to reload the OS's > or re-install SQL? Would it cause me to basically have to > backup all my SQl junk, install MSCS, and restore it? > > ******************************************************** This Weeks Sponsor: triCerat Inc. You need Day Zero Protection! Get Proactive with triCerat's Simplify Suite. Solve printing, security and profile problems before they occur. http://www.tricerat.com/?thethintl2 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm ThinWiki community - Excellent SBC Search Capabilities! http://www.thinwiki.com *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm