This wait accumulates during certain operations inside parallel queries. Bitmap, large binary objects and spooling operations can cause this wait type. This wait typically correlates with high CXPACKET waits and CPU utilization

Resolved by

DBAs and Developers

Suggested solutions

  1. Use Profiler/trace/Extended Events to determine the query causing the problem. Optimize this query to reduce the amount of parallelism required
  2. Investigate changing default MAXDOP and parallelism settings (links below)

Additional research

Doctor, this SQL Server appears to be sick
What MAXDOP setting should be used for SQL Server

See more

Consider using ApexSQL Monitor, a Windows and SQL Server monitoring tool able to track SQL Server wait types, including the individual query wait statistics

⇐ Back to index