(Republishing, or using this info in a commercial product/website, is prohibited without permission. All other uses are permitted. If in doubt, please ask.)

BROKER_TRANSMISSION_WORK

(Back to main page…)

Description:

Unknown, but it could be similar to BROKER_TRANSMITTER.

(Books Online description: “N/A”)

Questions/comments on this wait type? Click here to send Paul an email, especially if you have any information to add to this topic.

Added in SQL Server version:

2012

Removed in SQL Server version:

N/A

Extended Events wait_type value:

The map_key value in sys.dm_xe_map_values is 686 in 2012 and 704 in 2014 RTM. After 2014 RTM, you must check the DMV to get the latest value as some map_key values have changed in later builds.

Other information:

I have not seen this wait type be a noticeable contention point.

Known occurrences in SQL Server (list number matches call stack list):

  1. Unknown, but given the meaning of idempotent (reapplying it does not change the result) this could be for sending an operational directive that could end up being sent multiple times without a detrimental effect

Abbreviated call stacks (list number matches known occurrences list):

  1. SOS_Task::PostWait+9e
    EventInternal<SuspendQueueSLock>::Wait+2ca
    SOS_RWLock::GetLongWait+10b
    CSbTransmission::IdempotentWork+1e1
    CSbTransmission::IdempotentInvoke+dc
    CSbTransmission_Task::IdempotentInvoke+15
    CSbTaskManager::HandleReusableTask+2b8
    CSbTask::TaskStart+14b
    CSbTask::BeginTaskStart+17
    SOS_Task::Param::Execute+21e
    SOS_Scheduler::RunTask+a8