To upgrade SQL Compliance Manager 4.0 or later in a clustered environment using Windows Server 2003 or later, follow the steps below.
Be sure to back up your Repository and all databases and archives before upgrading SQL Compliance Manager.
Upgrade the SQL Compliance Manager Collection Service on Cluster Nodes
You must upgrade the SQL Compliance Manager Collection Service on each cluster node for the service to work correctly when a failure occurs on the primary cluster node hosting the Collection Service.
Before upgrading, changing, or uninstalling SQL Compliance Manager on the passive node, you must delete the following registry entry:
HKEY_LOCAL_MACHINE\Software\Idera\SQLcompliance\CollectionService\TraceDirectory. This step is unnecessary for new installations.
To upgrade the SQL Compliance Manager Collection Service on cluster nodes:
- In the Microsoft Cluster Administrator tool (Windows Server 2003) or Microsoft Failover Cluster Management Console (Windows Server 2008 and later), select the SQLComplianceCollectionService resource and take the service offline.
- Log on with an administrator account to the computer on which you want to upgrade SQL Compliance Manager.
SQLCMInstall.exein the root of the SQL Compliance Manager installation kit on the first cluster node.
- Review the information you need to start the upgrade and click Next.
Select the SQL Compliance Manager setup type and uncheck the IDERA Dashboard setup type. Review and accept the license agreement by selecting the I accept the terms and conditions of the End User License Agreement checkbox.
- Specify if you want to register SQL Compliance Manager with an existent IDERA Dashboard.
If you select Yes, you need to provide the IDERA Dashboard location and administrator credentials.
If you want to use the IDERA Dashboard, see how to Deploy the IDERA Dashboard in clustered environments.
- Specify the location in which you want to upgrade SQL Compliance Manager.
- Enable the Clustered Environment checkbox and select whether you are upgrading SQL Compliance Manager in an active or a passive node.
Verify that the repository is the same SQL Server Instance name hosting the current repository and specify a form of authentication.
Test Connections to make sure the information is correct and click Next.
- If you upgrade on the currently active node, verify that the trace directory is the same location in which your current directory resides, and click Next.
If you upgrade on a passive node, the wizard skips this step.
- Type the appropriate credentials in the provided fields under which the IDERA services run, and then click Next.
IDERA uses this account to connect, discover, and gather configuration information from SQL Servers in your Business environment, the installer grants the "Log on as a Service" right to the account that you specify.
- Review the upgrade settings and click Install.
- In Windows Services, stop the SQL Compliance Manager Collection service and set the Startup type to Manual.
Repeat the previous steps on each cluster node. Point to the SQL Compliance Manager Repository installed on the first node.
After upgrading SQL Compliance Manager in all nodes, follow the steps below:
- Log on to the active node and launch the Microsoft Cluster Administrator tool (Windows Server 2003) or the Microsoft Failover Cluster Management Console (Windows Server 2008 and later), right-click the SQLComplianceCollectionService resource, and select Properties.
- Go to the Registry Replication tab and set the Root Registry Key to
- Close the Properties window, right-click the SQLComplianceCollectionService resource, and bring the service online.
- Log on to the passive node, launch the Microsoft Cluster Administrator tool (Windows Server 2003) or the Microsoft Failover Cluster Management Console (Windows Server 2008 and later), and verify if the SQLComplianceCollectionService resource is online.