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 following notification will be displayed:

Cause

This issue is not caused by dbForge Monitor, but rather by limitations or configuration problems on the SQL Server instance itself. Common causes include:

1. Inactive or missing performance counters
2. Inadequate permissions for the SQL Server service account
3. Missing system libraries or dependencies
4. Issues introduced by a misconfigured or partial ssms installer setup

Additionally, users running an older version of SQL Server Management Studio may encounter such monitoring limitations. Ensuring a complete and up-to-date setup is important—consider using the latest SSMS 21 download for better reliability and compatibility.

Recommended Action

To resolve the issue:

1. Check SQL Server Configuration

1. Ensure that performance counters are enabled and properly configured.
2. Validate that the SQL Server instance has the required access rights to collect performance data.

2. Install Missing Dependencies

1. Address missing assemblies such as Microsoft.IdentityModel.Clients.ActiveDirectory by installing them or repairing your environment.

3. Update Your SSMS Installation

1. Use the latest SSMS 21 download to reduce compatibility issues and take advantage of updated monitoring features.
2. Ensure the installation was completed without errors using the official ssms installer.

4. Seek Additional Support

1. Contact Microsoft Support for official guidance.
2. Post your issue in SQL Server forums and DBA communities for practical insights.

• Related Articles

• 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 ...

• 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 ...

• 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 ...

• Timestamps Not in Expected Timezone in dbForge Studio for Oracle

  If you're encountering timestamps that don't match your system's timezone in dbForge Studio for Oracle, this can typically be resolved with a quick configuration update. This issue may arise due to default formatting settings or discrepancies in how ...

• Transaction Notification Is Not Displayed When VIEW SERVER STATE Is Missing

  The Notification if execution contains open transactions option works as expected on some SQL Server instances, but does not display any notifications on others. This behavior is typically caused by the absence of the VIEW SERVER STATE privilege for ...