Specifications
Enrolling SQL Server Instances CHAPTER 2 29
UCP Post-Installation Steps
When the Create Utility Control Point Wizard is closed, the Utility Explorer is invoked, and
you are automatically connected to the newly created UCP. The UCP is automatically en-
rolled as a managed instance. The data collection process also commences immediately. The
dashboards, status icons, and utilization graphs associated with the SQL Server Utility display
meaningful information after the data is successfully uploaded.
NOTE Do not become alarmed if no data is displayed in the dashboard and viewpoints in
the Utility Explorer Content pane; it can take up to 45 minutes for data to appear at rst.
All subsequent uploads generally occur every 15 minutes.
A benecial post-installation task is to conrm the successful creation of the UMDW. This
can be done by using Object Explorer to verify that the sysutility_mdw database exists on the
SQL Server instance. At this point, you can modify database settingssuch as the initial size
of the database, autogrowth settings, and le placementbased on the capacity planning
exercises discussed in the “UCP Sizing and Maximum Capacity Specications” section earlier
in this chapter.
Enrolling SQL Server Instances
After you have established a UCP, the next task is to enroll an instance or instances of SQL
Server into a SQL Server Control Point. Similar to deploying a Utility Control Point, this task is
accomplished by using the Enroll Instance Wizard in SSMS or by leveraging Windows Power-
Shell. The high-level steps afliated with enrolling instances into the SQL Server UCP include
choosing the UCP to utilize, specifying the instance of SQL Server to enroll, selecting the ac-
count to run the utility collection set, reviewing prerequisite validation results, and reviewing
your selections. The enrollment process then begins by preparing the instance for enrollment.
The cache directory is created for the collected data, and then the instance is enrolled into
the designated UCP.
IMPORTANT A UCP created on SQL Server 2008 R2 Enterprise can have a maximum of
25 managed instances of SQL Server. If more than 25 managed instances are required, then
you must utilize SQL Server 2008 R2 Datacenter.