Uninstall SQL Server using the following syntax:
Copy Code
start /wait setup.exe /qn VS=<VSName> INSTANCENAME=<InstanceName> REMOVE=SQL_Engine ADMINPASSWORD=<StrongPassword>
For the default instance, specify "MSSQLSERVER" for <InstanceName>.
The /qn switch suppresses all Setup dialog boxes and error messages. If the /qn switch is specified, all Setup messages, including error messages, are written to Setup log files. For more information about log files, see How to: View SQL Server 2005 Setup Log Files.
The /qb switch allows display of basic Setup dialog boxes. Error messages are also displayed.
Uninstall SQL Native Client, using the following syntax:
Copy Code
Start /wait <DVD Drive>\msiexec /qb /X <DVD Drive>\setup\sqlncli.msi
If SQL Server Setup fails to uninstall the cluster node, use the following steps:
Use the Registry Editor utility, regedit.exe, locate the registry key HLKM\Software\Microsoft\Microsoft SQL Server\<instid>\Setup, where <instid> is the specific SQL Server instance being uninstalled; for example, MSSQL.1 for the first instance and MSSQL.2 for the second instance.
Caution:
Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from editing the registry incorrectly can be resolved. Before editing the registry, back up any valuable data. For information about how to back up, restore, and edit the registry, see this Microsoft Knowledge Base article.
In this key, set SqlCluster=2.
Repeat the previous 2 steps to update the SqlCluster key on all nodes in the cluster.
Move the shared disk to the computer that is currently being uninstalled and, on that node, use Add or Remove Programs to remove SQL Server 2005.
Move the shared disk to the next node, and use Add or Remove Programs to remove SQL Server 2005.
Repeat this move-and-uninstall process for each remaining node.
Caution:
If SQL Server 2005 is running along with previous SQL Server versions, Enterprise Manager or other programs that depend on SQL-DMO, the previous versions may be disabled. This may occur in the following situations:
Side-by-side installations of SQL Server 2005, SQL Server 2000, and/or SQL Server 7.0, where any of the versions is uninstalled.
Side-by-side installations of SQL Server 2000 with SQL Server 2005, where SQL Server 2000 is installed after SQL Server 2005.