Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Make 'Excluded SQL' cascade to more pages than just the high-level SQL trend charts

Currently, excluded SQL only applies to the multi-day and one-day trend charts. The excluded SQL still shows up in reports, the wait event timings show up in the waits pages, etc. This makes it difficult to see what impact a dominant SQL statement has to the database as a whole, as well as over time.

Find more posts tagged with

Status: None

Comments

sainca

Apologies - additional scenario recorded in

+1 on THIS one.

Don't quite get the rationale as to why exclusion stops at high-level....... Is there a SW person who give a good use case for only 2 level, and not for lower, and reports, and current, too?