Professional Microsoft® SQL Server® 2008 Administration
by Brian Knight, Ketan Patel, Wayne Snyder, Ross LoForte, Steven Wort
8.3. Conversation Priorities
In SQL Server 2005, sending and receiving messages is handled on a first-come, first-served basis. In SQL Server 2008 you can set the priority for the conversations, which means messages from conversations that have high priority levels are typically sent or received before messages from conversations that have lower priority levels. You can set conversation priorities when you want certain types of messages to be processed first. For example, if you want certain users to run their reports first, you can set the priority high for their messages (queries) compared to other users, and Service Broker will process (run) those messages (queries) first.
8.3.1. Setting Conversation Priorities
The following example demonstrates the conversation priority:
Open the folder ConPriority under the Chapter 8 folder and double-click the ConPriority solution file. You need two instances of SQL Server connected to the same domain (as in Sample2). It is assumed that you understand how messages are delivered between two instances of SQL Server, as explained earlier in Sample2 in the section "Security Considerations for Service Broker."
Open the scripts CreateEndPointOnInitiator.sql and CreateEndPointOnTarget.sql. If you have already created Service Broker endpoints on your initiator and target servers (as explained in Sample2), then you can skip this step. Follow the instructions provided earlier in the "Windows Authentication" section to create the endpoints on the initiator ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access