Considerations for Running Utility and non-Utility Collection Sets on the Same Instance of SQL Server
Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).
The SQL Server Utility collection set is supported side-by-side with non- SQL Server Utility collection sets. That is, a managed instance of SQL Server can be monitored by other collection sets while it is a member of a SQL Server Utility. However, you must disable non- SQL Server Utility data collection functionality while the instance of SQL Server is being enrolled into the SQL Server Utility.
After the instance is enrolled with the UCP, you can restart non- SQL Server 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 SQL Server Utility collection sets side-by-side with non- SQL Server 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 SQL Server Utility.
To pass validation requirements, you must run the following stored procedures on the instance of SQL Server before you create a UCP, and on an instance of SQL Server before you enroll it into the SQL Server 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 SQL Server Utility UMDW (sysutility_mdw) for all collection sets on a managed instance of SQL Server.