How to Create a SQL Server Utility Control Point (SQL Server Utility)?

An enterprise can have multiple SQL Server Utilities, and each SQL Server Utility can manage many instances of SQL Server and data-tier applications. Every SQL Server Utility has one and only one utility control point (UCP). You must create a new UCP for each SQL Server Utility. Each managed instance of SQL Server and every […]

An enterprise can have multiple SQL Server Utilities, and each SQL Server Utility can manage many instances of SQL Server and data-tier applications. Every SQL Server Utility has one and only one utility control point (UCP). You must create a new UCP for each SQL Server Utility. Each managed instance of SQL Server and every data-tier application component is a member of one and only one SQL Server Utility, and is managed by a single UCP.

UCP "collects configuration and performance information from managed instances of SQL Server every 15 minutes. This information is stored in the utility management data warehouse (UMDW) on the UCP; the UMDW file name is sysutility_mdw. SQL Server performance data is compared to policies to help identify resource use bottlenecks and consolidation opportunities."

"SQL Server 2008 R2 offers new technologies to assist you with consolidation. Another new feature is the ability to convert an existing application into a data-tier app definition; this provides a convenient way to migrate an app's schema and logins because the data-tier app definition is designed to be more portable than a full SQL Server instance, and it encapsulates server-scoped objects such as logins. Note however that this process does not migrate data for the app between servers. You must perform data migration separately using backup and restore or another method.

For more information about how to convert an existing database to a data-tier application definition, see "How to: Extract a DAC".