BROKER_TRANSMISSION_WORK is one of the sparsely documented Service Broker waits; the best available understanding is that it behaves like BROKER_TRANSMITTER, threads in the message transmission machinery waiting for transmission work to become available. It sits in the same family as the transmission-object housekeeping waits.
Where documentation is thin, behaviour is the guide, and its behaviour is the familiar idle-Broker pattern.
Is It a Problem?
No observed case says so; it has not been a contention point, and it accumulates in Broker environments the way its transmitter siblings do, tracking idleness rather than load. Filter it with the rest of the Broker background set.
Anything real in Broker transmission shows up as unhappy rows in sys.transmission_queue, whose status text names the fault, or as activation and routing errors in the error log.
Common Causes
- Broker transmission machinery idling between message sends.
- Broker-enabled instances accumulating it alongside
BROKER_TRANSMITTER.
What To Do
- Filter it out of wait analysis.
- Route genuine delivery questions through
sys.transmission_queueand endpoint/routing configuration.
How To See It
Rank waits with Get-WaitStatistics; expect it only as Broker background noise.
Part of the SQL Server Wait Types Library.
Related deep dive: SOS_SCHEDULER_YIELD Wait Type.
Leave a Reply