This wait accumulates when a trace (commonly run as Profiler) has exhausted available buffers and is waiting free ones to become available (for disk writes). SQL Server by default has at least one trace configured to capture configuration changes and other events that could be useful should problems be detected. If the values are high please see the suggested solutions 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 Profiler 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