service-broker

问题 Currently we are using service broker to send the messages back and forth, which is working fine. But we wanted to group those messages by using the RELATED_CONVERSATION_GROUP. We wanted to use our own database persisted uuid as a RELATED_CONVERSATION_GROUP = @uuid from our database, but even though we use the same uuid every time the conversion_group_id comes different each time we receive the queue. Do you guys know what is wrong with way i am creating the broker or the receive call, i have

问题 Currently we are using service broker to send the messages back and forth, which is working fine. But we wanted to group those messages by using the RELATED_CONVERSATION_GROUP. We wanted to use our own database persisted uuid as a RELATED_CONVERSATION_GROUP = @uuid from our database, but even though we use the same uuid every time the conversion_group_id comes different each time we receive the queue. Do you guys know what is wrong with way i am creating the broker or the receive call, i have

问题 I am learning how to use the Service Broker of SQL Server 2008 R2. When following the tutorial Completing a Conversation in a Single Database. Following the Lesson 1, I have successfully created the message types, contract, the queues and services. Following the Lesson 2, I have probably sent the message. However, when trying to receive the message, I get the NULL for the ReceivedRequestMsg instead of the sent content. When looking at the sys.transmission_queue , the transmission_status for

问题 In the examples I can find of communicating between server instances using SQL Server Service Broker (here and here), route s are created to the MSDB database which is one of the system databases. For example use msdb; go create route [sender] with service_name = ‘sender’, address = ‘local’; go Why would I not create the route in the database that has the rest of the Service Broker objects such as message types and services? Is this how a production environment should do it? 回答1: Messages

问题 I cannot alter the service broker stored procedure, when I update the stored procedure it does not show any error and successfully gets updated but the changes does not come into affect. Is it because I need to stop the queue of the service broker on both databases before the changes could come into affect? Note: the service broker stored procedures produce and read xmls. INCLUDING THE STORE PROCEDURE ALTER PROCEDURE [dbo].[ServiceBroker_AtTarget

问题 The question is a continuation of the Service Broker: Designing the communication between two SQL servers (to make the earlier reasonably short). The answer to the above question suggested the usage of a simpler scenario of sending the regularly generated data via forever opened dialog. A trigger, that is responsible for forming the data at the satellite SQL server and sending it do the central SQL server, will probably use the fixed unique identifier. Anyway, the conversation must be started

问题 Does anyone know if there is a port that absolutely has to be open on the SQL server to allow service broker traffic? We were testing what happens when you close off all ports on the SQL server except (1433, 445, 3389) and the query notification still worked. We were under the impression that 4022 has to be open for the service broker to work we a default listening port. Is there a SQL system view that shows what port the service broker is communicating on? Is there a command to terminate all

问题 In my Local DB Sql Dependency works fine, but when i migrate to an Azure Database is not work. I check if service broker is enabled, and it is activated. This is the error: Statement 'RECEIVE MSG' is not supported in this version of SQL Server This is my code: public class Program { static void Main(string[] args) { SqlClientPermission permission = new SqlClientPermission(System.Security.Permissions.PermissionState.Unrestricted); if (SolicitarNotifications()) { string con = "Server=tcp:xxxxx

问题 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

问题 ( 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