Export (0) Print
Expand All

Enroll an Instance of SQL Server (SQL Server Utility)

Enroll an instance of SQL Server into an existing SQL Server Utility to monitor its performance and configuration as a managed instance of SQL Server. The utility control point (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.

In this release, the UCP and all managed instances of SQL Server must satisfy the following requirements:

  • SQL Server must be version 10.50 or higher.

  • The SQL Server instance type must be Database Engine.

  • The SQL Server Utility must operate within a single Windows domain, or domains with two-way trust relationships.

  • The SQL Server service accounts on the UCP and all managed instances of SQL Server must have read permission to Users in Active Directory.

  • The SQL Server instance to enroll cannot be SQL Azure.

In this release, the UCP must satisfy the following requirements:

  • The instance of SQL Server must be a supported edition. For a list of features that are supported by the editions of SQL Server, see Features Supported by the Editions of SQL Server 2012.

  • We recommend that the UCP is hosted by a case-sensitive instance of SQL Server.

  • Consider the following recommendations for capacity planning on the UCP computer:

    • In a typical scenario, disk space used by the UMDW database (sysutility_mdw) on the UCP is approximately 2 GB per managed instance of SQL Server per year. This estimate can vary depending on the number of database and system objects collected by the managed instance. The UMDW (sysutility_mdw) disk space growth rate is highest during the first two days.

    • In a typical scenario, disk space used by msdb on the UCP is approximately 20 MB per managed instance of SQL Server. Note that this estimate can vary depending on the resource utilization policies and the number of database and system objects collected by the managed instance. In general, disk space usage increases as the number of policy violations increases and the duration of the moving time window for volatile resources increases.

    • Note that removing a managed instance from the UCP will not reduce the disk space used by UCP databases until expiration of data retention periods for the managed instance.

In this release, all managed instances of SQL Server must satisfy the following requirements:

  • We recommend that if the UCP is hosted by a case-insensitive instance of SQL Server, then managed instances of SQL Server should also be case-insensitive.

  • FILESTREAM data are not supported for SQL Server Utility monitoring.

For more information, see Maximum Capacity Specifications for SQL Server and Features Supported by the Editions of SQL Server 2012.

For more information about SQL Server Utility concepts, see SQL Server Utility Features and Tasks.

Important note Important

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. Note, however, that all collection sets on the managed instance upload their data to the utility management data warehouse. For more information, see Considerations for Running Utility and non-Utility Collection Sets on the Same Instance of SQL Server and Configure Your Utility Control Point Data Warehouse (SQL Server Utility).

The following sections provide detailed information about each page in the Wizard work flow. Click on a link to navigate to details for a page in the Wizard. For more information about a PowerShell script of this operation, see the PowerShell example.

To launch the Wizard, expand the Utility Explorer tree on a utility control point, right-click on Managed Instances, and select Add Managed Instance….

To continue, click Next.

To select an instance of SQL Server from the connection dialog box, click Connect…. Provide the computer name and the SQL Server instance name in the format ComputerName\InstanceName. For more information, see Connect to Server (Database Engine).

To continue, click Next.

On the Connect to Server dialog box, verify the server type, computer name, and SQL Server instance name information. For more information, see Connect to Server (Database Engine).

Note Note

If the connection is encrypted, the encrypted connection is used. If the connection is not encrypted, SQL Server Utility reconnects using an encrypted connection.

To continue, click Connect….

Specify a Windows domain account to run the SQL Server Utility collection set. This account is used as the SQL Server Agent proxy account for the SQL Server Utility collection set. Alternatively, you can use the existing SQL Server Agent service account. To pass validation requirements, use the following guidelines to specify the account.

If you specify the SQL Server Agent service account option:

  • The SQL Server Agent service account must be a Windows domain account that is not a built-in account like LocalSystem, NetworkService, or LocalService.

To continue, click Next.

In this release, the following conditions must be true on the instance of SQL Server to be enrolled into the SQL Server Utility:

Condition

Corrective Action

You must have administrator privileges on the specified instance of SQL Server and on the UCP.

Log on with an account that has administrator privileges on the specified instance of SQL Server and on the UCP.

The SQL Server edition must support instance enrollment.

For a list of features that are supported by the editions of SQL Server, see Features Supported by the Editions of SQL Server 2012.

The SQL Server UCP should have TCP/IP enabled.

Enable TCP/IP on the SQL Server UCP.

The instance of SQL Server cannot already be enrolled with any other SQL Server UCP.

If the instance of SQL Server you specify is already managed as part of an existing SQL Server Utility, you cannot enroll it with a different UCP.

The instance of SQL Server cannot already be a UCP.

If the instance of SQL Server you specify is already a UCP that is different than the UCP you are connected to, you cannot enroll it in this UCP.

The instance of SQL Server must have SQL Server Utility collection sets installed.

Re-install the instance of SQL Server.

Collection sets on the specified instance of SQL Server must be stopped.

Stop pre-existing collection sets on the specified instance of SQL Server. If the data collector is disabled, enable it, stop any running collection sets, then re-run validation rules for the Create UCP operation.

To enable the data collector:

In Object Explorer, expand the Management node.

Right-click Data Collection, and then click Enable Data Collection.

To stop a collection set:

In Object Explorer, expand the Management node, expand Data Collection, and then expand System Data Collection Sets.

Right-click the collection set that you want to stop, and then click Stop Data Collection Set.

A message box will display the result of this action, and a red circle on the icon for the collection set indicates that the collection set has stopped.

The SQL Server Agent service on the specified instance of SQL Server must be started.

Start the SQL Server Agent service on the specified instance of SQL Server. If the specified instance of SQL Server is a SQL Server failover cluster instance, configure the SQL Server Agent service to start manually. Otherwise, configure the SQL Server Agent service to start automatically.

The SQL Server Agent service on the UCP must be started.

Start the SQL Server Agent service on the UCP. If the SQL Server UCP is a SQL Server failover cluster instance, configure the SQL Server Agent service to start manually. Otherwise, configure the SQL Server Agent service to start automatically.

WMI must be configured correctly.

To troubleshoot WMI configuration, see Troubleshoot the SQL Server Utility.

The SQL Server Agent proxy account must be a valid Windows domain account on the UCP.

Specify a valid Windows domain account. To ensure that the account is valid, logon to the UCP using the Windows domain account.

If you select the proxy account option, the SQL Server Agent proxy account must be a valid Windows domain account on the specified instance of SQL Server.

Specify a valid Windows domain account. To ensure that the account is valid, logon to the specified instance of SQL Server using the Windows domain account.

The SQL Server Agent service account cannot be a built-in account, like Network Service.

Re-assign the account to a Windows domain account. To ensure that the account is valid, logon to the specified instance of SQL Server using the Windows domain account.

The SQL Server Agent service account must be a valid Windows domain account on the UCP.

Specify a valid Windows domain account. To ensure that the account is valid, logon to the UCP using the Windows domain account.

If you select the service account option, the SQL Server Agent service account must be a valid Windows domain account on the specified instance of SQL Server.

Specify a valid Windows domain account. To ensure that the account is valid, logon to the specified instance of SQL Server using the Windows domain account.

If there are failed conditions in the validation results, correct the blocking issues and then click Rerun Validation to verify the computer configuration.

To save the validation report, click Save Report then specify a location for the file.

To continue, click Next.

The summary page lists the information about the instance of SQL Server to add to the SQL Server Utility.

Managed Instance Settings:

  • SQL Server Instance Name: ComputerName\InstanceName

  • Utility Collection Set Account: DomainName\UserName

To continue, click Next.

The Enrolling page provides status of the operation:

  • Preparing the instance for enrollment.

  • Creating the cache directory for the collected data.

  • Configuring the utility collection set.

To save a report about the enroll operation, click Save Report then specify a location for the file.

To complete the Wizard, click Finish.

Note Note

If you use SQL Server Authentication to connect to the instance of SQL Server to enroll, and you specify a proxy account that belongs to a different Active Directory domain than the domain where the UCP is located, instance validation succeeds, but the enrollment operation fails with the following error message:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Additional information: Could not obtain information about Windows NT group/user '<DomainName\AccountName>', error code 0x5. (Microsoft SQL Server, Error: 15404)

For more information about troubleshooting this failure, see Troubleshoot the SQL Server Utility.

Important note Important

Do not change any properties of the “Utility Information” collection set on a managed instance of SQL Server, and do not turn data collection on/off manually, as data collection is controlled by a Utility agent job.

After completing the Enroll Instance Wizard, click on the Managed Instances node in the Utility Explorer Navigation pane in SSMS. Enrolled instances of SQL Server are displayed in the list view in Utility Explorer Content pane.

The data collection process begins immediately, but it can take up to 30 minutes for data to first appear in the dashboard and viewpoints in the Utility Explorer content pane. Data collection continues one time every 15 minutes. To refresh data, right-click the Managed Instances node the Utility Explorer Navigation pane, then select Refresh, or right-click on the SQL Server instance name in the list view, then select Refresh.

To remove managed instances from the SQL Server Utility, select Managed Instances in the Utility Explorer Navigation pane to populate the list view of managed instances, right-click on the SQL Server instance name in the Utility Explorer Content list view, then select Make Instance Unmanaged.

Use the following example to enroll an instance of SQL Server into an existing SQL Server Utility:

> $UtilityInstance = new-object -Type Microsoft.SqlServer.Management.Smo.Server "ComputerName\UCP-Name";
> $SqlStoreConnection = new-object -Type Microsoft.SqlServer.Management.Sdk.Sfc.SqlStoreConnection $UtilityInstance.ConnectionContext.SqlConnectionObject;
> $Utility = [Microsoft.SqlServer.Management.Utility.Utility]::Connect($SqlStoreConnection);
> $Instance = new-object -Type Microsoft.SqlServer.Management.Smo.Server "ComputerName\ManagedInstanceName";
> $InstanceConnection = new-object -Type Microsoft.SqlServer.Management.Sdk.Sfc.SqlStoreConnection $Instance.ConnectionContext.SqlConnectionObject;
> $ManagedInstance = $Utility.EnrollInstance($InstanceConnection, "ProxyAccount", "ProxyPassword");
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft