Description
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
DBAs
Suggested solutions
- Determine who is reading the trace files and why
- Avoid trace analysis on production servers, copy the trace to a workstation and analyze on a local instance
- When collecting a trace only capture the appropriate events and columns. Filter when possible
- Ensure that the trace file is on a fast disk
Additional research
See more
Check out SpotLight, a free, cloud based SQL Server monitoring tool to easily detect, monitor, and solve SQL Server performance problems on any device