Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > Monitored SQL database server instance displays the incorrect database in DPA

Monitored SQL database server instance displays the incorrect database in DPA

Updated January 4, 2019

Overview

A monitored SQL Server database instance displays the incorrect database or text in DPA (for example, the database no longer exists).

Environment

  • All DPA versions
  • All monitored SQL Server versions

Cause

The first time DPA sees a SQL statement, DPA collects only SQL text. This is done to minimize the overhead on the monitored instances. The SQL statement may run against many databases within the same instance or even within any instance that DPA is monitoring.

DPA can be forced to recollect the SQL text by clearing old texts.

Resolution

Run the following script on your DPA repository database as the schema owner:

Select id, name from ignite.cond;

Choose the ID for the database instance with the hash_value.

Select * from ignite.const_@id
Where h = @hash_value
Delete from ignite.const_@id 
Where h = @hash_value

DPA recollects the SQL text in about two minutes (if it is running). 

 

Last modified

Tags

Classifications

Public