Managing the Core Database Engine - Microsoft SQL Server 2008 R2 Administration - page 111

F Utility Information—Utility Database FilesInfo
F Utility Information—Utility Performance Counters Items
F Utility Information—Utility Performance Counters Items1
F Utility Information—Utility Volumes Information
The non-utility data collection sets are installed when MDW wizard is completed, but not
started until they are enabled. The required schemas and their objects for the pre-defined
system collect sets are created when MDW is configured. The various UCP and MDW jobs are
created under SQL Server Agent | Jobs folder as follows:
F collection_set_1_noncached_collect_and_upload
F collection_set_2_collection
F collection_set_2_upload
F collection_set_3_collection
F collection_set_3_upload
F collection_set_4_noncached_collect_and_upload
F mdw_purge_data_[MDW]
F sysutility_get_cache_tables_data_into_aggregate_tables_daily
F sysutility_get_views_data_into_cache_tables
F sysutility_mi_collect_performance
F sysutility_get_cache_tables_data_into_aggregate_tables_hourly
F syspolicy_purge_history
F sysutility_mi_collect_and_upload
F mdw_purge_data_[sysutility_mdw]
The core schema is prefixed by 'core', which describes the tables, stored procedures, and
views that are used to manage and identify the collected data. These objects are locked and
can only be modified by the owner of the MDW database.
The parallel management of SQL Server Utility collection sets (utility and non-utility) requires
a preparation on the instance where UCP information is stored and the best practice is to
customize the data-collection frequency to avoid any overlap with the MDW data collection
schedule. The data collection store contains server activity for all the instances that are
configured to manage and host the operating system, such as percent CPU, memory usage,
disk I/O usage, network usage, SQL Server waits, and SQL Server activity.