This wait accumulates when SQL Server is requested to read a trace file. This typically occurs when an administrator accesses a trace through the sys.trace_gettable management view. Trace files are typically used for diagnostics and are used on an ad-hoc basis. Generally, it is safe to ignore. However, if the values are high please see the suggested solutions below

Resolved by


Suggested solutions

  1. Determine who is reading the trace files and why
  2. Avoid trace analysis on production servers, copy the trace to a workstation and analyze on a local instance
  3. When collecting a trace only capture the appropriate events and columns. Filter when possible
  4. Ensure that the trace file is on a fast disk

Additional research

Profiler Best Practices

⇐ Back to index