Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Database Performance Analyzer (DPA) > Missing SQL statistics when monitoring SQL Server 2005

Missing SQL statistics when monitoring SQL Server 2005

Table of contents
No headers


This article applies to DPA 8.0 and later.


DPA collects SQL execution statistics when monitoring SQL Server 2005 and later. If certain SQL statements are missing SQL execution statistics, it may be because:


SQL statistics collection was turned off for the monitored database instance.

  1. Click Options > Administration > Advanced Options > DB Instance Options.
  2. Click the Support Options check box.
  3. Select the database instance.
  4. Click the ENABLE_SQLSTATS option. If set to False, change to True.


The SQL buffer cache on the monitored database is too small or too many distinct SQL statements are executed on the monitored database. SQL statistics are queried every 10 minutes and compared to the previously queried values. If the same SQL statement cannot be found in the buffer cache after 10 minutes, no SQL statistics can be calculated for that SQL statement.


The SQL statement is contained within a stored procedure that has been compiled with the RECOMPILE option, or the SQL statement uses the RECOMPILE query hint. This causes SQL Server to recompile the stored procedure or statement before every execution and to not store the SQL plan in the buffer cache. If the SQL plan for the statement is not stored in the buffer cache, SQL Server does not track SQL statistics for that statement.

Last modified
15:18, 4 Jan 2016