service-broker

I'm new to Service Broker. We've set up a development system that appears to be working well. One strange thing I've noticed is that the conversation handles in the audit tables at each end of the Service Broker are different for the same message. I had assumed the same conversation handle would be used by the initiator and target ends so I'm wondering if we've got something configured wrong. Is it normal for a single message to have different conversation handles at each end of a conversation? Remus Rusanu There is a conversation_id , which is the same at both endpoints. And there is

The situation is closely related to SQL Service Broker - communication scenario - migration from SQL 2008 R2 to SQL 2014 and to SQL Service Broker -- one central SQL and more satelite SQL... beginner wants to understand details . After migration from SQL Server 2008 R2 Standard Ed. to SQL Server 2014 Standard Ed., the same code does not work. The firewall was set to allow the communication. The sys.transmission_queue (on both sender and receiver servers) keeps empty, and the GenericQueue (my identifier for the queue) receives the messages. However, the procedure attached by (to the receiving

We are developing an application that will use service broker to transfer messages from one database to another. SourceDB is used by an existing application from which we are siphoning off some data. TargetDB is used only by this application and processes/distributes the data we need. We are only using one type of contract and both DBs are on the same server. We have set up identical message types and contracts on both, and respective initiator and target queue/service. On both databases: ENABLE_BROKER is set TRUSTWORTHY is set Have a unique service_broker_guid Have sa as db owner, with all

( 2nd Update from 2012/12/06 -- new protocol, a sligtly different view) The question is whether the solution below seems reasonable for you, or whether there is any flaw that I did not notice (being quite new to SQL Server Service Broker)... I would like to continue in analysis of the problem presented in the SQL Service Broker: Collecting data from distributed sources . I would like to focus on the problem of protocol to be used when collecting data from the satellite SQL servers. The usage of the SQL Server Service Broker is a must -- it is dictated also by other reasons not presented here.

I am new to MS Sql's service broker. I've examined a couple of tutorials. But I could not find an answer. I have distributed servers, but luckily all of them are under the same domain. Is it possible to accomplish a structure without using any certificate? Remus Rusanu Yes. Do no use dialog security. Make sure all your BEGIN DIALOG statements use ENCRYPTION = OFF clause: BEGIN DIALOG @handle FROM SERVICE @from_service TO SERVICE @to_service ON CONTRACT @contract WITH ENCRYPTION = OFF; Grant SEND permission to [public] on each destinations service: GRANT SEND ON SERVICE::<servicename> TO