Page tree

The following instructions guide you through the installation of SQL Compliance Manager in a Windows Server 2012 based clustered environment. Be sure to have the following information available before creating the generic service:

  • Name of the disk containing the folder
  • SQL IP address
  • SQL network name
  • SQL Server service

Install the SQL CM Collection Service on Cluster Nodes

You must install 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 CM 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 install SQL CM services on cluster nodes:

  1. Log on with an administrator account to the computer on which you want to install SQL Compliance Manager.
  2. Run Setup.exe in the root of the SQL CM installation kit on the first cluster node.
  3. Under Install, click SQL Compliance Manager.
  4. Read the Welcome window, and then click Next.
  5. Review and accept the license agreement by clicking I accept the terms in the license agreement, and then click Next.
  6. Accept the default installation folder, or click Browse to specify a different folder, and then click Next.
  7. Select the Clustered Collection Server setup type, and then click Next.
  8. Check the Install the Collection Server in a Windows Cluster check box to note that you are installing the SQL CM components in a cluster. If you leave this box unchecked, the installer performs a Typical installation.
  9. Select whether you are installing the Collection Service on the Currently Active Node or A Passive Node, and then click Next.
  10. If you install on the currently active node, specify a trace directory on a shared disk, and then click Next. If you install on a passive node, continue with the next step.
  11. Type the service account information, and then click Next.
  12. Accept the default SQL Server hosting the Repository, or click Browse to specify a different server.
  13. Select the authentication method used to install the Repository database and include credentials, if required, and then click Next.
  14. Click Install.
  15. In Windows Services, stop the SQL CM Collection service and set the Startup type to Manual.

Repeat the previous steps on each cluster node. Point to the SQL CM Repository installed on the first node.

You cannot perform the installations concurrently, as the installers collide when checking the repository. You must perform the installations sequentially.

Create the clustered service resource

After installing the SQL Compliance Manager Collection Service on your cluster nodes, create the clustered service resource to allow SQL CM to recognize the cluster nodes.

To create the clustered service resource:

  1. Log onto the currently active cluster node using an administrator account, and then start the Microsoft Failover Cluster Manager.
  2. Right-click the SQL Server role, and then select Add Resource > Generic Service.
  3. Complete the New Resource Wizard to create the SQLcompliance Collection Service.
  4. Right-click the service you just created, and then select Properties.
  5. On the General tab, check the Use Network Name for computer name check box.
  6. Click Add to add a new root registry key.
  7. Type Software\Idera\SQLcompliance, and then click OK.
  8. Start the new generic service by bringing the resource online.

 

SQL Compliance Manager audits all activity on your server. Learn more > >