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 transmitter is waiting for work. Information from Microsoft®


Service Broker has a component known as the Transmitter which schedules messages from multiple dialogs to be sent across the wire over one or more connection endpoints. The transmitter has 2 dedicated threads for this purpose.

This wait type is charged when these transmitter threads are waiting for dialog messages to be sent using the transport connections.

High values of waiting_tasks_count for this wait type point to intermittent work for these transmitter threads and are not indications of any performance problem. If service broker is not used at all, waiting_tasks_count should be 2 (for the 2 transmitter threads) and wait_time_ms should be twice the duration since instance start up. 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_TRANSMITTER on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.

Prevalence of BROKER_TRANSMITTER across the Spotlight Population

For 20 % of hours with this wait, average wait time is less than 110 ms

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

201 instances contributed data to this chart

Latency Distribution of BROKER_TRANSMITTER across the Spotlight Population