This wait accumulates when a trace (commonly run as Profiler) is waiting for buffers to become available for writing. Not much is known about this wait type as it is not documented by Microsoft. 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. This wait is common and small values are generally acceptable. However, if the values are high please see the suggested solutions below

Resolved by


Suggested solutions

  1. Avoid running Profiler, use a scripted trace or Extended Events instead
  2. Do not run Profiler over the network
  3. When using Profiler or trace only capture the appropriate events and columns. Filter when possible
  4. Send trace output to file rather than to table
  5. Ensure that the trace destination file is to a fast disk

Additional research

Profiler Best Practices
Filtering Out Benign Waits

⇐ Back to index