service-broker

问题 After db restoring on other server the Service Broker is stopped. The restored db has a Trustworthy Off and now I set it to On to run Broker again. I understand that it is bad practice. Especially after reading articles by solomon-rutzky. I have made as Solomon advised for SQLCLR UNSAFE functions without setting database to TRUSTWORTHY ON. It works fine! How to restore Broker working in case TRUSTWORTHY OFF? 回答1: Trustworthy isn't required to run Service Broker. There is, however, an option

问题 After db restoring on other server the Service Broker is stopped. The restored db has a Trustworthy Off and now I set it to On to run Broker again. I understand that it is bad practice. Especially after reading articles by solomon-rutzky. I have made as Solomon advised for SQLCLR UNSAFE functions without setting database to TRUSTWORTHY ON. It works fine! How to restore Broker working in case TRUSTWORTHY OFF? 回答1: Trustworthy isn't required to run Service Broker. There is, however, an option

问题 I have gone through different questions/articles on Message Brokers and ESBs(Even on stackoverflow). Still not a clue as what is the CLEAR demarcating difference between an Message Broker and an ESB? Now here I am trying to compare products, Websphere Broker and Mule ESB!! Firstly , is (any version) Webshere Broker an ESB? Our IBM product guys claims it to be an ESB!(I am not surprised about that). My limited information tells me that a Message Broker works on a HUB-SPOKE model. However the

问题 I have gone through different questions/articles on Message Brokers and ESBs(Even on stackoverflow). Still not a clue as what is the CLEAR demarcating difference between an Message Broker and an ESB? Now here I am trying to compare products, Websphere Broker and Mule ESB!! Firstly , is (any version) Webshere Broker an ESB? Our IBM product guys claims it to be an ESB!(I am not surprised about that). My limited information tells me that a Message Broker works on a HUB-SPOKE model. However the

问题 I am trying an option BROKER_QUEUE_DISABLED in EVENT NOTIFICATION it seems it is not properly generating a Broker Queue disabled event. Can some one please validate the script which I created? (see below) Script: CREATE QUEUE NotifyQueue GO CREATE SERVICE NotifyService ON QUEUE NotifyQueue [http://schemas.microsoft.com/SQL/Notifications/PostEventNotification]); GO CREATE ROUTE NotifyRoute WITH SERVICE_NAME = 'NotifyService', ADDRESS = 'LOCAL'; GO CREATE EVENT NOTIFICATION [CHS

问题 Can someone explain conversation groups in service broker? Currently, I'm using service broker to send messages from one SQL server to another. On the sending server, I'm trying to correlate the messages so they are processed in serial on the receiving side. Based on the documentation, conversation groups seem to be a perfect fit for this, but on the receiving server, the messages get assigned to a different conversation group from the one I specified when sending the message. I've search

问题 I have SQL Service Broker set up between two servers over network and it is working alright. I'm implementing error processing at the moment. I have stored procedures attached to both queues to process messages. In the cases when sending a message fails, such as when attempting to send malformed XML, the message stays in the sender queue. The transmission status is Service Broker received an error message on this conversation. Service Broker will not transmit the message; it will be held

问题 I have a SQL Server CDC set up on few tables. Once the CDC is intiated the cdc tables are populated. I would want to process these changes and generate MQ messages for every change that occurs to send it to an external message queue. What is the best way to process this data. I have looked at few products like sqdata but I was thinking if there is any better way of doing it. I have looked at CDC with Service broker but this generates message to be send to an external application only. My

问题 I have an application that utilizes SqlDependency objects to track changes on certain tables of data in an underlying database. For the most part they work well, however, I noticed when I try to kill the dependency using the static Stop() method of the class, I get the following exception: A severe error occurred on the current command. The results, if any, should be discarded. Operation cancelled by user. That's about all the information the runtime provides. On the databases end the log is

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