Implementing Internal Activation
This tutorial is intended for users who are new to Service Broker, but are familiar with database concepts and Transact-SQL statements. It will help new users get started by showing them how to implement an internal activation stored procedure to process Service Broker messages.
This tutorial shows you how to create the database objects that are required to support a simple request-reply Service Broker conversation using an internal activation stored procedure. You will then start a conversation and use it to transmit messages.
Each Service Broker conversation has two ends: the conversation initiator and target. In a request-reply conversation, a request message us sent from the initiator to the target, which returns a reply message. Service Broker internal activation can be used to run a stored procedure whenever there are messages to process. Service Broker can run multiple copies of the stored procedure if there are many messages being transmitted. This tutorial shows you how to create a stored procedure that receives the request messages at the target, and how to configure the target to use internal activation to run the stored procedure.
You will perform the following tasks:
Create a service and queue for the target and a service and queue for the initiator.
Create a request message type and a reply message type.
Create a contract that specifies request messages go from the initiator to the target, and that reply messages go from the target to the initiator.
Create a stored procedure that receives request messages from the target queue and sends reply messages to the initiator.
Alter the target queue to enable internal activation of the stored procedure.
You will then perform a simple conversation:
Start the conversation.
Send a request from the initiator to the target.
Service Broker will then activate the stored procedure. The stored procedure will receive the request at the target and send a reply to the initiator.
Receive the reply at the initiator.
End the initiator side of the conversation.
Service Broker will then activate the stored procedure a second time, and the stored procedure will end the target side of the conversation.
Messages are not transmitted across a network for conversations that have both ends in the same instance of the Database Engine. Database Engine security and permissions restricts access to authorized principles. Network encryption is not needed for this scenario.
This tutorial is divided into three lessons:
To complete this tutorial, you should be familiar with the Transact-SQL language and how to use the Database Engine Query Editor in SQL Server Management Studio. You must be a member of the db_ddladmin or db_owner fixed database roles for the AdventureWorks sample database, or the sysadmin fixed server role.
Your system must have the following installed:
Any edition of SQL Server 2005 or SQL Server 2008.
Either SQL Server Management Studio or Management Studio Express.
Internet Explorer 6 or a later version.
The AdventureWorks sample database. For more information about how to install the sample databases, see Considerations for Installing SQL Server Samples and Sample Databases.
When you review the tutorials, we recommend that you add the Next and Previous buttons to the document viewer toolbar. For more information, see Adding Next and Previous Buttons to Help.