Why are a few database metrics in the Database tab showing empty values in the MS SQL monitor?

Why are a few database metrics in the Database tab showing empty values in the MS SQL monitor?

Before Applications Manager version 13910, we displayed high-level metrics for the MS SQL monitor’s database usage using SQL Server performance counters.

From version 13910 onwards, we fetch detailed database-level metrics. As a result, some metrics may show empty values if the required data is not available from the SQL Server.


But from Applications Manager version 13910, we display the detailed usage of data files and log files (Database Disk Utilization), VLF details, DBCC information, and mirroring details. This requires a connection to each database present in the SQL Server with db_datareader permission.

Please refer to our prerequisites link regarding permissions. In case the SQL user used for monitoring doesn't have the mentioned permission — either to connect to the respective database or to execute the data collection query—then the particular database metrics will be shown as empty on the Database page.


If you are on the latest version (above 13900) and do not wish to provide db_datareader permission for each database, you can revert to the old view by enabling the Disable connections to database(s) checkbox available under:
Info
Settings → Performance Polling → MS SQL → Database → Disable connections to database(s)



How to switch to the old view of the Database tab?
If you're using a version above 13900 and do not wish to provide db_datareader permission for each database, you can switch back to the old view by enabling the configuration key directly in the backend database. To do this:
  1. Connect to the Applications Manager backend database.
  2. Execute the following query:
Info
UPDATE AM_GlobalConfig SET VALUE='true' WHERE NAME='updateOldVersionModelForMSSQLDBDetails';
  1. Restart the Applications Manager service.
  2. Check the Database tab in the MS SQL monitor to confirm the change.

Notes
Note: If you switch back to the old UI, you will no longer be able to monitor the following metrics:
  1. Individual Data files & Log files (Database Disk Utilization)
  1. VLF (Virtual Log File) Details
  1. DBCC (Database Console Command) Information
  1. Mirroring Details
These metrics are available only in the latest version that connects to each database individually.

                  New to ADSelfService Plus?

                    • Related Articles

                    • Why are thresholds and alerts not working in Database tab metrics of MS SQL monitor?

                      In Applications Manager's MS SQL monitor, metrics under the Database tab are collected once every hour by default. This is controlled by the 'Collect data in every hour' option under Settings → Performance Polling → MS SQL → Metric Name: Database, ...
                    • Self monitor Applications Manager using Real User Monitoring

                      We can monitor the Applications Manager using Real User Monitoring with a Java Script injection and this can be used to measure the Applications Manager's performance continuously. All you need is to install and setup the Real User Monitoring (RUM) ...
                    • Troubleshooting MS SQL Monitor Addition Problems

                      1. Ensure that the SQL Server is running and accessible. Try connecting to the SQL Server instance via SQL Server Management Studio or DBVisualizer using the same credentials. This step helps diagnose connection issues, ensuring that both the server ...
                    • Database Query Monitor FAQ

                      How to fix an "Unable to find the Primary Key for tablename" error displayed after adding a query monitor? After adding a Database Query Monitor, users must select and update a Primary Key for each table. The primary key can be a single column or a ...
                    • How is Backup Age calculated for MS SQL DB monitor?

                      Backup Age displays the number of hours passed since the backup operation was completed. In simple terms, it is the difference between the current time and the time at which backup was performed. Backup Age (hours) = Current Time - Backup Time By ...