If you encounter 'The user does not have permission to perform this action' message while running the query, then update the permission for the specified SQL user and execute the query again.

Scenario I: If the query does not return any result, you'll need to check if you have enabled performance counters for your MSSQL server.
There are two ways to check if performance counters have been enabled for your MSSQL server.

Method 1:
Start > Run > Perfmon.exe > MonitoringTools > Performance Monitor > Click “Add Counters…+” -> check if "<SQLSERVER/MSSQL$InstanceName>:x" counters are available, where x stands for the following counters: AccessMethods, Availability Replica, Buffer Manager, Database Replica, Databases, General Statistics, Latches, Locks, Memory Manager, Plan Cache, SQL Statistics.

select * from sys.dm_os_performance_counters

If the above query does not return a list of all performance counters, then it might not be enabled for your MSSQL server. 

Follow the steps below to enable performance counters for your MSSQL server:

1. Open cmd prompt in administrator mode.
   

2. Navigate to MSSQL Installation bin directory (Default Directory: C:\Program Files\Microsoft SQL Server\MSSQL14.SQLXE\MSSQL\Binn).
   

3. Run the below commands:
   
   For SQL servers Using Default Instance:
   unlodctr MSSQLSERVER
   lodctr perf-MSSQLSERVERsqlctr.ini
   For SQL servers Using Named Instance:
   unlodctr MSSQL$InstanceName
   lodctr perf-MSSQL$InstanceNamesqlctr.ini

  

4. Restart the services "Remote Registry" and "Performance Logs & Alerts" by  executing the following commands:
   
   net stop "Remote Registry"  &&  net start "Remote Registry"  
   net stop "Performance Logs & Alerts" && net start "Performance Logs & Alerts"
   
   

   
   
   

5. After performing all the above steps, check if Performance counters have been enabled using Method 1 or 2 mentioned above.
   
   If performance counters have not been enabled yet, check the registry hives and keys (it’s not recommended to do any changes at the registry level as doing so could lead to instability on the operating system. If you choose to do these changes, you should have a backup of the Operating System and Registry, to recover them if necessary). The following registry keys should exist and must have a valid configuration:
   
   

1. Library
   

2. Open
   

3. Collect
   

4. Close
   

5. PerfIniFile
   
   
   

Note: The Registry Path is as follows:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\<<service name>>\Performance]

You should also check if there’s a key named "Disable Performance Counters" inside HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib directory.



If it is configured with the value 1, you must configure it with value 0. This should allow you to rebuild the registry counters and help files.

Refer here for more detailed information.

After following the above steps, check the query result and 'Overview' page of the reported MS SQL monitor after polling. If the problem persists, check Scenario II as well.

Scenario II: If the query returns the desired result, it indicates that data collection has happened. Now, poll your monitor in Applications Manager and verify if data is populated in the 'Overview Tab'.

If data is not populated, share the below information with us for further analysis:

1. Output for the below queries by using the same SQL user used in Applications Manager for monitoring:
   

select * from sys.dm_os_performance_counters

select * from sysperfinfo 

      2.  Version of the SQL Server that you are checking