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 Service Broker destination list that is associated with a target service is updated or re-prioritized. Information from Microsoft®


This wait type is charged when next hop destination list associated with a target service/broker instance pair gets updated or re-prioritized due to addition or removal of a dialog to the target service/broker instance pair. Service Broker sends messages to these next hop destinations in the order of their priority and hence it needs to serialize access to destination-list and their effective priority changes.

Waiting_tasks_count and wait_time_ms for this wait type merely indicate the number of times Service Broker had to serialize access to these internal structures with avg_wait_time_ms being really small. 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_SERVICE on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.

Prevalence of BROKER_SERVICE across the Spotlight Population

For 83 % of hours with this wait, average wait time is less than 0.023 ms

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

29 instances contributed data to this chart

Latency Distribution of BROKER_SERVICE across the Spotlight Population