I have 2 x data centers.
DC 1 and DC 2 both are on the same domain with different IP ranges.
there are 2 SQL Servers in DC1, 2 x SQL Servers in DC2
I want to implement Always-on availability groups across them.
What is the preferred approach, Distributed Availability Groups or regular Availability Groups and why specifically?
Cheers
June 10, 2020 at 5:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
So If you want a way to join two SQL environments together with SQL Always on availability groups, maybe these environments are on different OS versions which makes stringing a cluster across all nodes impossible this is a good solution.
It does have its drawbacks, Distributed Availability Groups do not have a separate listener, instead, it utilizes the listeners of the 2 separate AGs to create a group. this means is you want to modify your connections strings to point to a single listener you can not and therefore you will have to modify all application connectivity strings unless you can implement a workaround. This was probably the main reluctance for using it however if utilizing in Azure cross-region the Primary Replica updates the Secondary (Primary know as the forwarder) only which inturn sync with the other secondary replicas in the secondary region which would save traffic going over the vnet peer so there would be a cost saving there.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply