May 31, 2019 at 12:00 am
Comments posted to this topic are about the item Service Broker Queues
May 31, 2019 at 5:26 am
Nice question to end the week on, thanks Steve
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
May 31, 2019 at 3:15 pm
good question, cheers Steve
---------------------------------------------------------------------------------------
The more you know, the more you know that you dont know
May 31, 2019 at 6:37 pm
I haven't used these yet. Just wondering, what are some of the things people in this group have used Service Broker queues for?
May 31, 2019 at 7:59 pm
I haven't used these yet. Just wondering, what are some of the things people in this group have used Service Broker queues for?
With my current, it is used to transfer data between databases in different netork domains, where domain trust goes against company policy, in seperate locations in our country
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
May 31, 2019 at 9:54 pm
We use it to transfer realtime data from one system to another. Mostly as a way to break reliance on linked servers where possible.
We pull data from system X into system Y. Application A uses system X and Application B uses system Y. Application A relies heavily on the tables not being locked and blocking needs to be minimized as much as possible to prevent slowdown on the system. Application B needs to validate data from system X with the data being as near to real time as possible so SSIS isn't an option. It works well for us for the most part.
Database mirroring also uses service broker in the back end to do its magic.
You can also do a 1 to many with service broker by sending multiple messages on table change. If you have a busy server with high CPU, high memory and high disk I/O, you may want to offload some of the auditing data to a less busy server. Or really, any cross database/instance/server communication you want to do.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply