Timeline for SQL Server, ServicerBroker for asynchronized execution of stored procedures
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 10, 2017 at 18:58 | comment | added | Laughing Vergil | Let us continue this discussion in chat. | |
| Jan 10, 2017 at 18:58 | comment | added | Laughing Vergil |
Ignore what I said above. When I reviewed the article and queue handling in Service broker, I realized that the key is in the CREATE QUEUE statement.
|
|
| Jan 10, 2017 at 18:57 | comment | added | user114705 | How to look into queue ? Sorry for my dummy questions, but I am starting at this subject. | |
| Jan 10, 2017 at 18:55 | comment | added | user114705 |
And, from what proc_BrokerTargetActivProc know that it should get messages from TASK_QUEUE. In this procedure there is no this information
|
|
| Jan 10, 2017 at 18:54 | comment | added | user114705 | Is it difficult to call procedure with additional parameter? | |
| Jan 10, 2017 at 18:48 | comment | added | user114705 |
When it comes to above example (link) ? Who call proc_BrokerTargetActivProc ?
|
|
| Jan 10, 2017 at 18:47 | comment | added | Laughing Vergil |
3) [a] conversation_handle is a Service Broker UniqueIdentifier for the message queue, saved in the variable @RecvReqDlgHandle. [b] message_bodyis the actual message that was placed on the queue, saved in @RecvReqMsg for processing after it is pulled off of the queue. [c] message_type_name lets the receiving process understand what type of message was sent. As an example, if a message queue was set up to handle all inserts and updates to table Customers, the receiver needs to know if a given message was an Insert message or an Update message. This would be where that info was passed.
|
|
| Jan 10, 2017 at 18:41 | comment | added | Laughing Vergil |
1) The Service Broker is the service used to manage the queues in this case. Other situations might use RabbitMQ or another external message queue handler. 2) In general: proc_BrokerTargetActivProc will either be activated by a SQL Server job, a startup procedure, or on the start of an application that needs the proc to handle messages. The exact startup mechanism depends on what you need and when you need it.
|
|
| Jan 10, 2017 at 18:32 | vote | accept | CommunityBot | ||
| Jan 10, 2017 at 18:32 | comment | added | user114705 |
1.Could you explain me, what are services here ? In reference to queue nad procedures. 2. Who execute proc_BrokerTargetActivProc procedure ? (which in real is infinite loop getting one message from queue). 3. What does it mean these parameters?: @RecvReqDlgHandle = conversation_handle, ` @RecvReqMsg = message_body, ` ` @RecvReqMsgName `
|
|
| Jan 10, 2017 at 17:55 | history | answered | Laughing Vergil | CC BY-SA 3.0 |