May 26, 2015 at 2:54 am
Hi Guys,
I was at an interview for a company that uses the Service Broker for their DR model - the chap wouldn't go into much detail on how or even why, other than stating failover latency.
So, its piqued my interest - has anyone ever seen this use for the service broker before? Or used it?
Is there a benefit of the usual logshipping vs mirroring vs whatever
Cheers
Alex
ps. I annoyingly tend to use the terms DA and HA interchangeably. Sorry!
May 26, 2015 at 3:26 am
Never seen anything like that before. SQL Server already has several HA features and I suspect that using SB for something it wasn't meant for would be a total train wreck.
-- Gianluca Sartori
May 26, 2015 at 3:32 am
That's extremely weird and would require a hell of a lot of custom development. Sounds like someone wanted to do things the hard way.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 9, 2015 at 7:49 pm
There are very few ways to scale out MSSQL, and by that I mean writes. SSB is one option to handle multi-master write mirroring, where you can't get away with just having a single-master hot/warm (or primary/secondary) setup. Usually queuing/routing/prioritization/etc is better suited up the app stack but SSB can be used as a simple replay mechanic.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply