Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Database Performance Analyzer (DPA) > Troubleshoot WMI configuration for SQL Server resource metrics

Troubleshoot WMI configuration for SQL Server resource metrics

Table of contents

Updated March 11th, 2016

Overview

Some of the SQL Server database resource metrics require access to the WMI performance counters on the server running the monitored SQL Server instance.  There are a number of configuration issues which can prevent access to these counters by DPA.

Environment

All DPA versions

Steps

WMI permissions

The account running the SQL Server intance must have the necessary permissions to access the WMI counters in the root\cimv2 namespace.  The user must have at least  the Execute Methods and Enable Account permissions.

After modifying these privileges, it may be necessary to restart the Windows Management Instrumentation service.

 

1. Enable WMI counters.

The SQL Server database resource metrics rely on two WMI performance counters: PerfOS and PerfDisk. You must enable these counters for DPA to access the necessary resource data. You can check if these counters are disabled by using the Extensible Performance Counter List tool from Microsoft.

2. Select the counters named PerfOS and PerfDisk in the Extensible Performance Counters list. If the Performance Counters Enabled check box is not checked, then the counter is disabled.

You can also check if these counters are disabled using the Registry Editor.

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PerfDisk\Performance\Disable Performance Counters = 0x1
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PerfOS\Performance\Disable Performance Counters = 0x1


The 0x1 value means disabled. If this key is not present, or is set to 0x0, then the counter is enabled.

 

3. Run SQLServer and SQLAgent under a domain account.

When running SQLServer and SQLAgent Windows services under a domain account:

  • Use SQL Configuration Manager to assign the account and login details instead of editing the service login account directly. By using SQL Configuration Manager, the proper directory permissions are granted as needed for the desired account. Editing the services directly does not perform this necessary step.
  • Make sure that the domain account used for SQLServer and SQLAgent is added to the Local Administrators group on the server.
  • If you want to use Kerberos authentication, a manual SPN will need to be added to AD by an account with domain administration rights. Normally, SQL Server handles this on its own when running under the standard account for a default installation, but cannot when running under a domain account (unless said account also has domain admin privileges which is not recommended).


After making these changes, restart the SQL Server and SQL Agent services.

Last modified

Tags

Classifications

Public