Waitopedia is a comprehensive resource of information about SQL Server waits.

The description shown below is the top answer as voted by the Spotlight community.

The charts are based on 2.1 TB of data collected from 4207 instances uploaded by 323 Spotlight users over an 8 week period.


Category: Idle
SQL Server versions: 2008, 2008 R2, 2012, 2014, 2016, 2017

This is an idle wait and so it can be safely ignored.


2 Answers


Occurs when the SQL Trace rowset trace provider waits for either a free buffer or a buffer with events to process. Information from Microsoft®


I noticed this wait while running a SQL Profiler Trace with the intention of running the tuning advisor. The query I was running is very intensive and long (1+ minute) so I'm guessing that the trace was back-logged or something along those lines. [Steve Hilker]

Very rare

This wait never occurs for most instances

For each of 4207 instances, we ranked TRACEWRITE on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.

Prevalence of TRACEWRITE across the Spotlight Population

For 93 % of hours with this wait, average wait time is around 2 seconds

For each instance, we found all the recent hours when it had a TRACEWRITE wait. We found the average latency for each of those hours.

234 instances contributed data to this chart

Latency Distribution of TRACEWRITE across the Spotlight Population