Why are some metrics in the Database tab of the MS SQL monitor showing empty values?
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 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 SQL Server with db_datareader permission.
Note: 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:
Settings → Performance Polling → MS SQL → Database → Disable connections to database(s)
Switching 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:
- Connect to the Applications Manager backend database.
- Execute the following query:
UPDATE AM_GlobalConfig SET VALUE='true' WHERE NAME='updateOldVersionModelForMSSQLDBDetails';
- Restart the Applications Manager service.
- Check the Database tab in the MS SQL Monitor to confirm the change.
Note: If you switch back to the old UI, you will no longer be able to monitor the following metrics:
- Individual Data files & Log files (Database Disk Utilization)
- VLF (Virtual Log File) Details
- DBCC (Database Console Command) Information
- Mirroring Details
These metrics are available only in the latest version that connects to each database individually.
Refer to our feature page to learn more about SQL Server monitoring in Applications Manager.
New to ADSelfService Plus?
Related Articles
Why are thresholds and alerts not working for metrics in the Database tab of the MS SQL monitor?
By default, Applications Manager collects metrics under the Database tab of the MS SQL monitor once every hour. The Collect data control this behavior in every hour option under: Settings → Performance Polling → MS SQL → Metric Name: Database Since ...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 issues while adding an MS SQL Monitor
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 do I resolve the "No Data" issue for MS SQL performance metrics?
Problem: If the metrics in the MS SQL monitor's 'Overview' page aren't getting populated, it might be due to any of the following reasons: MS SQL user does not have permission to access the performance counters. Data collected from SQL Server is not ...