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: 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017

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


2 Answers


Occurs when a task is currently performing common language runtime (CLR) execution and is waiting for a particular autoevent to be initiated. Long waits are typical, and do not indicate a problem. Information from Microsoft®


If you have a SQL CLR application, you may notice that waits on CLR_MANUAL_EVENT and CLR_AUTO_EVENT from sys.dm_os_wait_stats are very high. This is normal and can be safely ignored because these waits reflect internal CLR runtime waits under normal conditions. ...

Read more at: http://blogs.msdn.com/b/psssql/archive/2008/02/05/high-waits-on-clr-manual-event-and-clr-auto-event.aspx

Very rare

This wait never occurs for most instances

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

Prevalence of CLR_AUTO_EVENT across the Spotlight Population

For 74 % of hours with this wait, average wait time is less than 10 minutes

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

612 instances contributed data to this chart

Latency Distribution of CLR_AUTO_EVENT across the Spotlight Population