August 2012
Intermediate to advanced
1416 pages
33h 39m
English
SQL Server has no user interface to monitor Service Broker activity. You can however make use of one or more of the following resources described in Table 25.1.
Table 25.1 Resources to Monitor Service Broker Activity
| Resource | Description |
| SQL Profiler | SQL Profiler provides the same 13 trace events available since SQL Server 2005. |
| Extended Events | Extended Events is the preferred method for troubleshooting and monitoring Service Broker activity. For a complete list and description of the Service Broker events available in SQL Server 2012, refer to http://technet.microsoft.com/en-us/library/ms186347.aspx. |
| ssbdiagnose Utility | The ssbdiagnose utility introduced in SQL Server 2008R2 is still supported and is a great way to easily report issues in Service Broker conversations or service configuration issues. For more information on the ssbdiagnose utility, refer to http://msdn.microsoft.com/en-us/library/bb934450.aspx. |
| Catalog Views | SQL Server 2012 provides 12 catalog views for Service Broker. Table 25.2 lists and describes each of these Catalog Views. |
| Dynamic Management Views (DMVs) | SQL Server 2012 provides four basic DMVs to monitor tasks, messages, queues, and connections. Table 25.3 lists and describes each of these DMVs. |
Table 25.2 describes the Service Broker Catalog Views available in SQL Server 2012.
Table 25.2 Service Broker Catalog Views
| Catalog View | Description |
| sys.conversation_endpoints | This catalog view contains a ... |
Read now
Unlock full access