Open for Voting

Exclude SQL statement history from trend analysis when SQL statement is excluded

When a SQL Statement is added to the exclude list, the history of that SQL statement is still considered as valid for an alarm condition in DPA. When a SQL Statement is excluded from trend analysis, the history for that statement should also be excluded from the alarm algorithm so that it no longer triggers an alarm when it is excluded. Currently, the history is still considered by the algorithm until the detail data for that SQL statement ages off at the 30-day interval.

  • I probably used the wrong terminology when writing this feature request.  When I said "alarm", I meant the Query status summary was still showing as red for that server when all query analysis items for that server had been excluded in the SQL exclusion list.  We expected that server to drop off the Query Analysis Warning/Critical issues count immediately.