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: 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017

This is an idle wait and so it can be safely ignored.


2 Answers


Occurs when the RECEIVE WAITFOR is waiting. This is typical if no messages are ready to be received. Information from Microsoft®


This wait type is charged once per WAITFOR RECEIVE SQL statement, where the statement execution waits for messages to arrive in the user queue.

Waiting_tasks_count must be same as the number of times such statements have been executed and wait_time_ms should be the total time their execution had to wait before messages arrived or WAITFOR timeout for each.

If avg_wait_time_ms is much higher than expected, errorlog and profiler events should be checked on both initiator and target server instances for potential problems. 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_RECEIVE_WAITFOR on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.

Prevalence of BROKER_RECEIVE_WAITFOR across the Spotlight Population

For 40 % of hours with this wait, average wait time is less than 16 seconds

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

345 instances contributed data to this chart

Latency Distribution of BROKER_RECEIVE_WAITFOR across the Spotlight Population