November 28, 2012 at 8:53 am
Can someone please direct me to some hardcore evidence that FIRE and FORGET set up is not good and can cause x amount of issues.
I need something written by a MVP or something directly from MS. To prove my point.
Tempdb is filling up, sys.conversation_endpoints is clearing out but I believe that is due to the END CONVERSATION With Clean up.
Service broker spid has been identified as the culprit.
My impressions are that the endpoints/Work tables are being left in the TEMPDB. The last status of the conversation is DI DISCONNECTED_INBOUND. Remote side has issued end convo but the target hasn’t ended properly.
I need this to be proven to cause issues to force a rewrite of the SB.
November 28, 2012 at 9:50 am
i found a few articles, all with explanations:
http://www.nootz.net/index.php/service-broker-fire-and-forget-messages.html
Lowell
November 28, 2012 at 10:13 am
rusanu.com is a good source. I'd ask him further questions if you need them. He's done a lot of SB work.
November 28, 2012 at 10:38 am
Thanks
Both of you.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply