Professional Microsoft® SQL Server® 2008 Administration

8.4. Administering Service Broker

Service Broker is integrated with the Database Engine, so administrating Service Broker application is a part of your day-to-day activities. This section describes the different tasks involved in administering a database that hosts a Service Broker application. Most administrative tasks are part of the normal administration of your database. Of course, there are some special things you have to do for a Service Broker application.

8.4.1. Installing Service Broker Application

You learned earlier that the key components to develop a Service Broker application are message types, contracts, queues, services, routes, endpoints, and stored procedures. When a development team provides the installation script for a Service Broker application, those scripts typically include T-SQL statements. A typical Service Broker application has an initiator, which resides on a server, and a target, which may reside on the same server in the same database, or in a different database, or even on a different server. Obviously, complex Service Broker applications may involve more than a couple of servers communicating with one another. In general, you should have separate scripts, for installation on the initiator and on the target.

8.4.1.1. Preparing the Databases

When messages are sent from one database to another, Service Broker uses a unique identifier to route the messages to the correct database. That unique identifier is called Service Broker GUID. The Service_Broker_Guid ...