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 a task is waiting in the primary event handler of the Service Broker. This should occur very briefly. Information from Microsoft®


Each SQL server instance has a primary event handler thread for processing Service Broker start up/shutdown and timer events. This thread never goes away and is always either waiting for such events or processing them.

This wait type is charged each time Service Broker's primary event handler waits for instance start up/shutdown or any dialog timer events (dialog timeouts) and mirrored routes timeouts.

Wait_time_ms for this wait type should approximately be equal to the interval since instance start up. Waiting_tasks_count merely indicates the number of times the primary event handler had to wait due to absence of any events.

Neither of these two fields in the DMV indicates any performance issue in the engine. If Service Broker is not being used at all (either directly or through DBMail, Event Notification), then max_wait_time_ms and wait_time_ms would approximately be the same and waiting_tasks_count would be really small value. Source: http://blogs.msdn.com/b/sql_service_broker/archive/2008/12/01/service-broker-wait-types.aspx

Very rare

This wait never occurs for most instances

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

Prevalence of BROKER_EVENTHANDLER across the Spotlight Population

For 67 % of hours with this wait, average wait time is less than 4.4 minutes

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

508 instances contributed data to this chart

Latency Distribution of BROKER_EVENTHANDLER across the Spotlight Population