Hello,
I read that is there is this Database setting for service broker: ERROR_BROKER_CONVERSATIONS
I have not understood the how to use this setting in real scenario.
Could somebody provide me some practical example?
White papers are also ok! :-)
Thank you
Marina B.
The primary reason this option was introduced is for the scenarios when two databases that have conversations with each other and one of them has an incident and data loss occurs (it has to be restored back in time). Since the conversations between the two databases are now out of sync, the one that was restored back in time should ERROR_BROKER_CONVERSATIONS in order to error all existing conversations before enabling the broker. The application should be prepared to deal with the Error message anyway, and this is a quick way to send an Error message on all conversations. After this, the broker in the database is enabled and keeps the old broker instance (aka. service_broker_guid, thus all routes to it are still valid).
No comments:
Post a Comment