INSTALLING UTILITIES ON A SECOND NODE
* TIP: INSTALLING UTILITIES ON A SECOND NODE
(contributed by Richard Waymire, rwaymi@microsoft.com)
Q. How do you install the client utilities on the second node of a SQL Server 7.0 machine in a cluster configuration? After you install Microsoft Cluster Server (MSCS) and SQL Server and you run the wizard to create your virtual SQL Server, you have a SQL Server implementation that you can switch from one Windows NT server to the other. The problem is that the client utilities, such as Microsoft Management Console (MMC) and the Query Analyzer, are installed only on the primary node. The installation program won't let you install these utilities on the second node because, according to Microsoft, you might overwrite .dll files and other executables. Microsoft says that you have to uncluster the SQL Server machine, install the utilities on the second node, then cluster the servers again. This is a fairly radical and error-prone solution. Is there another way to do it?
A. After you've clustered a SQL Server 7.0 machine, you must uncluster it before you can install the tools on the second node. Yes, it's a nasty procedure. And yes, Microsoft has fixed this problem in SQL Server 2000, which installs the tools locally on all clustered nodes. Microsoft also updated the clustering white paper "How to Install SQL Server 7.0 Enterprise Editions on Microsoft Cluster Server" at http://www.microsoft.com/sql to address tool installation. Note that SQL Server 7.0 installs the tools on the cluster disk, so the tools fail over when SQL Server fails over. However, the shortcuts don't fail over, so you need to navigate to the mssql7binn directory and run the .exe file to restore the shortcuts.
|