For databases using Service Broker. This wait accumulates while Service Broker is forwarding messages to another node. This wait was introduced in SQL Server 2012, is uncommon and currently is not documented by Microsoft. High values are not expected and should be investigated

Resolved by


Suggested solutions

  1. If values are excessively high, ensure Service Broker objects are designed as per best practice (link below)
  2. Check the SQL Server error log for any Service Broker related issues

Additional research

Service Broker: Periodic Tasks
Service Broker: Performance and Scalability Techniques
How to troubleshoot Service Broker problems

See more

Consider using ApexSQL Monitor, a Windows and SQL Server monitoring tool able to track SQL Server wait types, including the individual query wait statistics

⇐ Back to index