No, Service Broker uses conversation group locking to ensure that two
threads aren't processing messages n the same dialog simultaneously.
Obviously if two threads were processing the same dialog, message ordering
wouldn't be possible. In addition, the locks were extended to groups of
conversations to be locked to handle the problems created by related
messages from different sources being processed simultaneously. This is
different than the locking for dialog ordering. Bottom line, Service Broker
ensures message ordering within a dialog but it does nothing for the
ordering of messages between dialogs in a conversation group. In fact,
messages from different dialogs within a conversation group are not
generally delivered in the received order if multiple messages from multiple
dialogs are received.

Signature
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
> In BOL, it says that SQL Server uses Conversation Groups to provide
> exactly-once-in-order access to messages, but how can this be if each
[quoted text clipped - 5 lines]
> Thanks,
> Wells
Wells Caughey - 30 Jan 2006 14:19 GMT
Ok, now I understand. Thanks for the clarification.
Wells
> No, Service Broker uses conversation group locking to ensure that two
> threads aren't processing messages n the same dialog simultaneously.
[quoted text clipped - 18 lines]
>> Thanks,
>> Wells