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: Other
SQL Server versions: 2008, 2008 R2, 2012, 2014, 2016, 2017


2 Answers


Occurs when initializing Service Broker in each active database. This should occur infrequently. Information from Microsoft®


This wait type is charged each time Service Broker fails to initialize internal broker managers for any database. Service Broker waits for about 1 second before re-attempting to initialize broker for same database. These events should be rare.

Waiting_tasks_count for this wait type is the number of times Service Broker failed to initialize broker on any database. Wait_time_ms will be proportional to waiting_tasks_count with avg_wait_time_ms being close to 1 second.

High or increasing values of waiting_tasks_count for this wait type indicate some problem in the SQL instance. 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_INIT on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.

Prevalence of BROKER_INIT across the Spotlight Population

For 95 % of hours with this wait, average wait time is around 990 ms

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

29 instances contributed data to this chart

Latency Distribution of BROKER_INIT across the Spotlight Population