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 > Exclude a SQL Statement from DPA data collection

Exclude a SQL Statement from DPA data collection

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,513 Votes: 0 Revisions: 9

 

It may be helpful to exclude SQL statements from the DPA performance data collection module. For example, you can exclude SQL statements associated with backups, replication, and so on.

 

  1. Click Options > Support > Database Query Tool.
  2. You need the DPA ID for the database instance and the DPA ID for the SQL statement you want to exclude.

 

DPA database instance ID

select ID, name from cond;

Copy and paste the ID value into the INSERT statement below replacing the <dbid> placeholder.

 

DPA ID for SQL statement

In DPA, click the SQL statement where it appears in one of the legends. You will see the SQL text along with the ID (Hash) for the statement. Copy and paste that number into the INSERT statement below replacing the <sql> placeholder.

 

INSERT the SQL into CON_QP_EXCLUDE (8.1 and earlier)

INSERT INTO con_qp_exclude (dbid, type, value) VALUES (<dbid>, 'H', '<sql>');

 

INSERT the SQL into CON_QP_EXCLUDE (8.1 and later)

INSERT INTO con_qp_exclude (dbid, type, value, origin) VALUES (<dbid>, 'H', '<sql>', 'U');

 

All future data collection will exclude this SQL statement.  No past data will be purged as a result, but the SQL statement will eventually age out of all charts in DPA.

Last modified

Tags

Classifications

Public