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 notice that CPU metrics are not displayed for some of the active connections. An example of this issue is shown below.



The following notification will be displayed:

Cause

This issue is related to the SQL Server instance itself and not to dbForge Monitor. The lack of CPU data may be due to limitations or configuration issues on the server side that prevent performance counters or relevant metrics from being accessed or reported.
Since this is a server-side issue, we suggest the following:
  1. Contact Microsoft Support for official troubleshooting and resolution steps.
  2. Post your issue on specialized SQL Server forums to seek advice from the community and database professionals.

    • Related Articles

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

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

    • dbForge SQL Tools Missing After Installing or Updating SSMS

      Typically, upon the initial launch of SSMS after you install SQL Tools for the first time, there is a brief registration process that takes no more than 1-2 minutes, depending on your system's performance. If SQL Tools are still missing after this ...

    • How to Start dbForge Products with Logging for Studios, Standalone Tools, and MiniTools

      If a dbForge product crashes or becomes unresponsive upon startup, logging is required for a detailed record of failures and issues. This guide helps you launch dbForge products with logging enabled to capture essential information for ...