Skip to content

Latest commit

 

History

History
41 lines (30 loc) · 3.2 KB

File metadata and controls

41 lines (30 loc) · 3.2 KB
title Run Utility and non-Utility Collection Sets on Same SQL Instance | 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 ca7ee9b3-ef9a-4ba4-83d0-9ee9f80dab27
author MikeRayMSFT
ms.author mikeray

Run Utility and non-Utility Collection Sets on Same SQL Instance

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] The [!INCLUDEssNoVersion] Utility collection set is supported side-by-side with non- [!INCLUDEssNoVersion] Utility collection sets. That is, a managed instance of [!INCLUDEssNoVersion] can be monitored by other collection sets while it is a member of a [!INCLUDEssNoVersion] Utility. However, you must disable non- [!INCLUDEssNoVersion] Utility data collection functionality while the instance of [!INCLUDEssNoVersion] is being enrolled into the [!INCLUDEssNoVersion] Utility.

After the instance is enrolled with the UCP, you can restart non- [!INCLUDEssNoVersion] Utility collection sets. Note, however, that all collection sets on the managed instance will upload their data to the utility management data warehouse (UMDW); the UMDW file name is sysutility_mdw.

To run [!INCLUDEssNoVersion] Utility collection sets side-by-side with non- [!INCLUDEssNoVersion] Utility collection sets, consider the following points:

  • Side-by-side collection sets are supported.

  • You must disable existing data collectors while enrolling instances into the [!INCLUDEssNoVersion] Utility.

  • To pass validation requirements, you must run the following stored procedures on the instance of [!INCLUDEssNoVersion] before you create a UCP, and on an instance of [!INCLUDEssNoVersion] before you enroll it into the [!INCLUDEssNoVersion] Utility:

    exec msdb.dbo.sp_syscollector_set_warehouse_database_name NULL  
    exec msdb.dbo.sp_syscollector_set_warehouse_instance_name NULL  
    

    If you do not run these stored procedures before you launch the Create UCP Wizard or Add Managed Instance Wizard, the operation will fail.

  • You must use the [!INCLUDEssNoVersion] Utility UMDW (sysutility_mdw) for all collection sets on a managed instance of [!INCLUDEssNoVersion].

See Also

SQL Server Utility Features and Tasks
Configure Your Utility Control Point Data Warehouse (SQL Server Utility)