CPU Metrics Not Displayed in dbForge Monitor for SQL Server

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

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

    • How to Connect to MySQL Server

      In the second article of the series uncovering how to get started with MySQL, we talk about the ways of connecting to MySQL Server. You can connect to MySQL Server using MySQL Client, dbForge Studio for MySQL, and MySQL Workbench. In this article, we ...

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

    • How to Enable Logging for Source Control and Data Pump for SQL Server

      Logging is essential for capturing detailed information about failures and issues in the program. If reproducing or diagnosing a problem is difficult, logging helps in providing a deeper investigation. This guide applies to the following products: ...

    • Limit of activations exceeded (dbForge)

      The point is that when you change any hardware part of your computer or reinstall the OS or change a profile on your computer, your Hardware ID changes so the software considers it as an installation on an alternative computer. Virtual machine ...