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 there is contention to access the state of a Service Broker connection endpoint. Access to the state for changes is serialized. Information from Microsoft®


This wait type is charged each time there is some state change for a Service Broker (or Database Mirroring) connection endpoint during the connection establishment (i.e. handshake) phase - e.g. initialization before connect or after accept, login negotiation (authentication, encryption), validation, error, arbitration and error. This wait type is also charged per connection endpoint every time sys.dm_broker_connections (or sys.dm_db_mirroring_connections) DMV is queried to serialize access to each connections handshake state.

Avg_wait_time_ms for this wait type should be very small and the wait_time_ms and waiting_tasks_count should both be proportional to the number of times Service Broker (or Database Mirroring) establishes connection with some other SQL server instance and the number of times sys.dm_broker_connections (or sys.dm_db_mirroring_connections) DMV is queried.

Rapidly increasing values of wait_time_ms and waiting_tasks_count for this DMV could indicate very frequent connection establishment (and teardown). Since service broker transport tears down connections after ~90 seconds of inactivity, these values can increase if applications use service broker once every ~90 seconds. 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_ENDPOINT_STATE_MUTEX on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.

Prevalence of BROKER_ENDPOINT_STATE_MUTEX across the Spotlight Population

For 100 % of hours with this wait, average wait time is above 1 ms

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

1 instance contributed data to this chart

Latency Distribution of BROKER_ENDPOINT_STATE_MUTEX across the Spotlight Population