CPU Utilization Metric Is Empty or Shows 0 in SQL Monitor

The CPU Utilization metric in SQL Monitor is not displayed or always shows 0.

The same SQL Monitor instance may work correctly for other SQL Server instances. For example, CPU utilization can be displayed normally on SQL Server 2016 while remaining unavailable on another server.

Cause

SQL Monitor retrieves CPU utilization data from the sys.dm_os_performance_counters dynamic management view.

If the SQL Server performance counters are disabled or not functioning correctly, the DMV returns zero values, causing the CPU Utilization metric to remain empty or display 0.

This is a known Microsoft issue that has been observed on different SQL Server versions, including SQL Server 2008 through SQL Server 2022.

The issue is not related to insufficient permissions. If the monitoring account lacked access to the DMV, SQL Monitor would report a permission error rather than displaying zero values.

Diagnostics

Run the following query on the affected SQL Server instance:

SELECT

      instance_name,

      counter_name,

      cntr_value

FROM sys.dm_os_performance_counters WITH (NOLOCK)

WHERE object_name LIKE '%Resource Pool Stats%'

AND counter_name LIKE '%CPU%'

​

If all values returned in the cntr_value column are equal to 0, the issue originates on the SQL Server side rather than in SQL Monitor.

Resolution
Since SQL Monitor relies on SQL Server performance counters to collect CPU usage statistics, the issue must be resolved on the SQL Server side.

Investigate the status of SQL Server performance counters or contact Microsoft Support for further assistance.

• Related Articles

• CPU Metrics Not Displayed in dbForge Monitor for SQL Server

  Symptoms When using dbForge Monitor for SQL Server, you may observe that CPU metrics are not displayed for certain active connections. For instance, the CPU usage section might be empty or missing data, as illustrated in the example below: The ...

• Changing Connections Is Not Supported for Non-Empty Query Documents

  Attempting to change the connection for a query document may result in the following error: "Cannot change the connection for a non-empty query document" As a result, the connection cannot be switched to another server or environment while the ...

• dbForge SQL Tools Missing After Installing or Updating SSMS

  When launching SQL Server Management Studio (SSMS) for the first time after installing dbForge SQL Tools, a brief initialization process is expected. This typically takes 1–2 minutes depending on system performance. If the tools—such as SQL ...

• Silent installation of ADD-in Tools (i.e., dbForge SQL Complete) with custom IDE selection.

  dbForge SQL Complete can be installed in silent mode (without user interaction) using a configuration file (.ini). This file allows you to define in which IDEs (SSMS or Visual Studio) the integration should be performed. It also includes parameters ...

• How to Enable Logging for SQL Complete

  Logging is a standard mechanism used in many software tools to capture detailed information about application behavior, errors, and performance issues. It is particularly useful when diagnosing problems that are difficult to reproduce or analyze in ...