This wait accumulates when a trace (commonly run as Profiler) is waiting for event processing to complete in order for the trace to shutdown. This wait type is uncommon and generally occurs because a trace has been configured to capture too many events. As traces are generally used for diagnostic purposes this wait typically does not effect end-users. If values are excessive see suggestions below

Resolved by


Suggested solutions

  1. When using Profiler or trace only capture the appropriate events and columns. Filter when possible
  2. Do not run traces over the network
  3. Send trace output to file rather than to table
  4. Ensure that the trace destination file is to a fast disk

Additional research

Profiler Best Practices

⇐ Back to index