March 9, 2023 at 10:24 am
Hi.
SQL Version 2017 .
I have one existing ALWAYSON AG setup. I want to setup transactional replication On top of AG, Does Distributor database can able to configure and choose primary, secondary replica nodes while configure distributor role? please suggest.
Or Remote distributor choose?
Thanks
March 9, 2023 at 12:12 pm
Distribution database can be put into the AOAG if you are running CU6 or above
The below will detail how to set this up and ensure that each replica can connect to the distribution DB and make replication work
March 9, 2023 at 1:11 pm
Thanks for sharing.
In Existing ALWAYSON AG setup, will it possible to configure Publisher role and Distributor role on same existing ALWAYSON AG ? or Does it require distributor role another separate remote instance?
March 9, 2023 at 3:08 pm
Reading all the documentation it requires the distributor to be on a separate instance.
March 9, 2023 at 4:22 pm
I did this as a proof of concept on 2017 and it was pretty ugly getting it to work and to keep it working consistently through failover. The replications were supposed to be going away anyways so we just pushed that effort of eliminating the replications ahead of the SQL migration. If transactional replication were reliable, I would have been fine with a tough set up if there was low chance of it breaking afterwards but couldn't trust it to not break and not have a long recovery time. Maybe it has improved on 2019, but it was not fun at all on 2017 circa ~CU10
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply