Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > SQL Server bug prevents collection of resource statistics

SQL Server bug prevents collection of resource statistics

DPA does not collect numerous resource statistics for early releases of SQL Server. This is due to a memory leak in SQL Server caused by SQL Server stored procedures (sp_OAMethod and sp_OAGetProperty) that are called to collect these resources. WMI metric queries can become unresponsive, leave orphaned connections and may require restarting the monitored instance to resolve.


See the following Microsoft articles for more information on the memory leak:


SQL Server versions that do not exhibit the memory leak (DPA collects all resource statistics for these versions):

  • SQL Server 2000 SP4 or higher
  • SQL Server 2005 SP3 or higher
  • SQL Server 2008


If your SQL Server instance is at or above these versions, resource statistics may not be collected for other reasons. See this article.

Resource statistics not collected for early SQL Server versions

  • Memory Paging Rate (pages/sec)
  • % O/S Memory Utilization
  • % O/S CPU Utilization
  • O/S CPU Queue Length
  • O/S Disk Queue Length
  • Physical I/O Rate (KB/sec)
  • Physical Read Rate (KB/sec)
  • Physical Write Rate (KB/sec)
Last modified