Skip to content

Latest commit

 

History

History
44 lines (30 loc) · 3.9 KB

File metadata and controls

44 lines (30 loc) · 3.9 KB
title Move a UCP from One Instance of SQL Server to Another (SQL Server Utility) | Microsoft Docs
ms.custom
ms.date 03/14/2017
ms.prod sql
ms.prod_service database-engine
ms.reviewer
ms.technology configuration
ms.topic conceptual
ms.assetid b402fd9e-0bea-4c38-a371-6ed7fea12e96
author MikeRayMSFT
ms.author mikeray

Move a UCP from One Instance of SQL Server to Another (SQL Server Utility)

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] This topic describes how to move a utility control point (UCP) from one instance of [!INCLUDEssNoVersion] to another in [!INCLUDEssCurrent] by using [!INCLUDEssManStudioFull].

Using SQL Server Management Studio

Move a UCP from one instance of SQL Server to another.

  1. Create a new UCP on the instance of [!INCLUDEssNoVersion] that will be the new host instance of the UCP. For more information, see Create a SQL Server Utility Control Point (SQL Server Utility).

  2. If non-default policy settings have been set for any instances of [!INCLUDEssNoVersion] in your [!INCLUDEssNoVersion] Utility, make note of the policy thresholds so that you can re-establish them on the new UCP. Default policies are applied when instances are added to the new UCP. If default policies are in effect, the [!INCLUDEssNoVersion] Utility list view displays Global in the Policy Type column.

  3. Remove all managed instances from the old UCP. For more information, see Remove an Instance of SQL Server from the SQL Server Utility.

  4. Back up the utility management data warehouse (UMDW) from the old UCP. The filename is Sysutility_mdw_<GUID>_DATA, and the database default location is <System drive>:\Program Files\Microsoft SQL Server\MSSQL10_50.<UCP_Name>\MSSQL\Data\, where <System drive> is normally the C:\ drive. For more information, see Copy Databases with Backup and Restore.

  5. Restore the backup of the UMDW to the new UCP. For more information, see Copy Databases with Backup and Restore.

  6. Enroll instances into the new UCP to make them managed by the [!INCLUDEssNoVersion] Utility. For more information, see Enroll an Instance of SQL Server (SQL Server Utility).

  7. Implement custom policy definitions for the managed instances of [!INCLUDEssNoVersion], as necessary.

  8. Wait approximately 1 hour for data collection and aggregation operations to complete.

  9. To refresh data, right-click the Managed Instances node in Utility Explorer, then select Refresh. List view data are displayed in the Utility Explorer content pane. For more information, see View Resource Health Policy Results (SQL Server Utility).

See Also

SQL Server Utility Features and Tasks
Enroll an Instance of SQL Server (SQL Server Utility)