Page tree

The following instructions guide you through the installation of SQL Diagnostic Manager in a Windows Server 2008 based clustered environment.

Things to consider before you install SQL Diagnostic Manager in a clustered environment

  • Create a separate cluster resource group to host SQLDM services. A separate group allows the SQLDM services to fail without causing other resources in the group to failover.
  • Before you create this separate cluster resource group, gather a dedicated IP, NetBIOS name, and a dedicated disk for the cluster resource group.
  • SQLDM Collection, Management, and Predictive Analytics services can run as generic services on your newly-created cluster resource group.
  • The system may request the network Name and network IP as part of cluster configuration.

Install SQLDM Services on Cluster Nodes

You must install the SQLDM services on each cluster node for the services to work correctly when a failure occurs on the primary cluster node hosting the SQLdm services.

To install SQLDM services on cluster nodes:

  1. Log on with an administrator account to the computer on which you want to install SQLDM.
  2. Run Setup.exe in the root of the SQLDM installation kit on the first cluster node.
  3. Click SQL Diagnostic Manager on the Quick Start window.
  4. On the Welcome window of the setup program, 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 Change to specify a different folder, and click Next .
  7. Select the Typical setup type and click Next.
  8. Select the SQL Server instance and enter a database name.
  9. Enter the service account information and click Next.
  10. Click Install.
  11. In Windows Services, stop the SQLdm Management service and set the Startup type to Manual.
  12. In Windows Services, stop the SQLdm Collection service and set the Startup type to Manual.
  13. In Windows Services, stop the SQLdm Predictive Analytics service and set the Startup type to Manual.

Repeat the previous steps on each cluster node. Point to the SQLDM 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.

Configure the Cluster Resource Group

Cluster Resource Group settings must be modified to allow SQL Diagnostic Manager to recognize the cluster nodes.

To configure the Cluster Resource Group:

  1. Select a disk that is configured in the Cluster Resource Group and create a directory on that disk that you want to use to hold local data for the services.
  2. On the primary node, edit the registry and add a new key named Default to the key \Software\Idera\SQLdm. In this key add a string value called DataPath. Set its value to the full path to the data directory created in step 1 (as shown in the image at the end of the steps).
  3. In the Failover Cluster Management tool, right-click on Services and Applications and select Configure a Service or Application.
    • Provide a name for the service
    • Select Generic Service
    • Select the SQLDM Management Service
    • Enter the network name and IP address for the services
    • Select the clustered storage that hosts the path defined in step 1
    • Skip the Registry Replication
    • Verify the settings and click Next to complete the wizard
  4. In Services and Applications, click the newly created service name in the Other Resources section and then on the SQLDM Management service and take it offline.
  5. In Services and Applications, right-click on the newly created service and then on the SQLDM Management Service and select Properties.
    • On the General tab, select Use Network Name for computer name
    • On the Dependencies tab, add the name of service and disk, and then click Apply
    • On the Registry Replication tab, if blank, add SOFTWARE\Idera\SQLdm\Default\DataPath
  6. In Services and Applications, right-click the newly created service and select Add a Resource and Generic Service.
  7. Select the SQLDM Collection Service.
  8. Select Next and finish out the wizard.
  9. In Services and Applications , right-click on the newly created service and then on the SQLDM Collection Service and select Properties.
    • On the General tab, select Use Network Name for computer name
    • On the Dependencies tab, add name of service and disk, and then click Apply
    • On the Registry Replication tab, add SOFTWARE\Idera\SQLdm\Default\DataPath
  10. In Services and Applications, right-click the newly created service and select Add a Resource and Generic Service .
  11. Select the Predictive Analytics service from the list of resources.
  12. Select Next and then Finish to exit the wizard.
  13. In Services and Applications, click the newly-created service and then on the SQLDM Predictive Analytics service and select Properties .
    • On the General tab, select Use Network Name for computer name
    • On the Dependencies tab, add the name of the service and disk, and then click Apply
    • On the Registry Replication tab, if blank, add SOFTWARE\Idera\SQLdm\Default\DataPath
  14. In Windows Services, bring the SQLdm Management service resource online.
  15. In Windows Services, bring the SQLdm Collection service resource online.
  16. In Windows Services, bring the SQLdm Predictive Analytics service resource online.
  17. On the active node on which you installed the SQLdm services, use the Management Service Configuration wizard (Start > All Programs > IDERA> SQL Diagnostic Manager > Tools > Management Service Configuration Wizard) to force the services to re-register.
  18. Test the configuration from the Management Service Configuration wizard before finishing the wizard.

Complete the Cluster Configuration in SQL Diagnostic Manager

Start the SQLDM Desktop Client and select SQLDM Repository. If the SQLDM Repository is clustered make sure to use the virtual server name for the SQL Server hosting the SQLDM Repository.


SQL Diagnostic Manager identifies and resolves SQL Server performance problems before they happen. Learn more > >