Use the following steps to upgrade your SQL Diagnostic Manager installation in a clustered environment.
SQL Diagnostic Manager 10.0 and later requires Microsoft SQL Server 2005 running on the computer that hosts the SQL Diagnostic Manager Repository database for all installations.
Upgrade in a Microsoft Windows Server 2003 Clustered Environment
To upgrade SQL Diagnostic Manager in a clustered environment:
- Log on to the cluster node using the Administrator account.
- In Cluster Administrator, select the resource group that contains the SQL Diagnostic Manager services.
- Take the SQLDM Management and Collection services off line.
Perform the following steps on each node, starting with the active node:
- Upgrade SQL Diagnostic Manager components previously deployed to the node.
- In Windows Services, stop the SQLDM Collection, SQLDM Management, and SQLDM Predictive Analytics services.
- Set the SQLDM services to manually start, and then restart the services.
Once the previous steps are complete, perform the following steps on each cluster node:
- In Cluster Administrator, bring the SQLDM Management Service on line.
- Use the Management Service Configuration wizard to force the services to re-register on the active node.
Upgrade in a Microsoft Windows Server 2008 Clustered Environment
To upgrade SQL Diagnostic Manager in a clustered environment:
- Log on to the cluster node using the Administrator account.
- In the Failover Cluster Management tool, select the resource group that contains the SQL Diagnostic Manager services.
- Take the SQLdm Management and Collection services offline.
Perform the following steps on each node, starting with the active node:
- Upgrade SQL Diagnostic Manager components previously deployed to the node.
- In Windows Services, stop the SQLDM Collection, SQLDM Management, and SQLDM Predictive Analytics services.
- Set the SQL Diagnostic Manager services to manually start, and then restart the services.
Once the previous steps are complete, perform the following steps on each cluster node:
- Bring the SQLdm Management Service on line.
- Use the Management Service Configuration wizard to force the services to re-register on the active node.