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

Include highest DOP for a parallelized query in stats for historical reference

This kind of information could help in troubleshooting CXPACKET waits and significant overhead associated with parallelization for the SQL Server database engine.

Would you rather have the true wait type be shown (cpu, I/O, etc.) rather than the top wait of a parallel query as cxpacket? Vote this up to show detail of child processes and real waits instead of CXPACKET.

Find more posts tagged with

Status: None

Comments

FormerMember

Addition or re-word to the request: Would you rather have the true wait type be shown (cpu, I/O, etc.) rather than the top wait of a parallel query as cxpacket?

FormerMember

Currently, if a SQL has N threads (say 10), 9 of them could be waiting on 1 doing I/O for instance. The total weight of the query is the sum of the weight types, meaning CXPacket will show up as the dominant wait. This is a benign weight type as those threads are not consuming much resource while waiting on their brother doing the I/O. The true weight for the query is the sum of the actual weights that consume resource. (In this example, I/O).