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 the Service Broker queue task handler tries to shut down the task. The state check is serialized and must be in a running state beforehand. Information from Microsoft®


Service Broker has several task handlers to execute broker internal tasks related to transmission of messages, asynchronous network operations and processing of received messages.

This wait type is charged only when one of these task handlers is stopping due to absence of broker internal tasks. The task handler waits for maximum 10 seconds before getting destroyed in case it needs to be restarted to execute some task.

Waiting_tasks_count and wait_time_ms should both be small values for heavy Service Broker usage scenarios. In addition, every 5 seconds, Service Broker schedules an internal cleanup task that does not do much work when broker is not being used. But, it causes one of the task handlers to wake-up, restart, execute the task and then start waiting again. As a result, even though Service Broker is not used at all, waiting_tasks_count and wait_time_ms for this wait type keep increasing, proportional to the interval since instance start up with avg_wait_time_ms being close to 5 seconds. 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_TASK_STOP on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.

Prevalence of BROKER_TASK_STOP across the Spotlight Population

For 28 % of hours with this wait, average wait time is less than 530 ms

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

1062 instances contributed data to this chart

Latency Distribution of BROKER_TASK_STOP across the Spotlight Population