Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Server & Application Monitor (SAM) > AppInsight for SQL Performance Counter not found and restoration steps

AppInsight for SQL Performance Counter not found and restoration steps

Updated: 3-20-2017


You may encounter an issue with AppInsight for SQL Performance Counter not displaying in SAM. When viewing the AppInsight for SQL page and related resources, you may receive an error "Performance counter not found." For an example, see the following screenshot:




  • All SAM versions
  • AppInsight for SQL


Check for counters

To resolve, you first need to check for counters on the SQL database that is monitored by AppInsight for SQL (not the Orion SQL database). 

  1. Access the monitored SQL database that displays the error message.
  2. Run the following query to verify if counters are present:
    RTRIM(object_name) as Category,
    RTRIM(counter_name) as [Counter],
    RTRIM(instance_name) as Instance,
    cntr_value as RawValue,
    cntr_type as CounterType
FROM sys.dm_os_performance_counters
ORDER BY CASE cntr_type WHEN 1073939712 THEN -1 ELSE cntr_type END

After running, you should see results like the following:


Results: If the query returns no values, you may have an issue with your SQL Server installation. You will need to contact Microsoft regarding this issue.

Use the Instance name column to find the name of the missing database and the counter it is associated with. If it does not exist for the counter, then the above errors are valid and you will need to work with your DBA / Microsoft to resolve the issue.

Remove Startup Parameter to attempt displaying counters

During the initial configuration of SQL Server, DBAs may disable the SQL Server Performance monitor counters to reduce SQL overheads. This is optional as certain diagnostics become unavailable, such as Parameter -x (see the screenshot below).


To access the SQL server properties screen, open the SQL Server Configuration Manager tool and look at the properties for that service.


Remove the Startup Parameter and Reboot the SQL Server.

Check to see if the Performance Counters are being created now by running the script in Check for counters.


Last modified
11:14, 30 Mar 2017