December 17, 2020 at 7:51 pm
Hello,
I have transactional replication setup with several databases. The publisher and subscriber have drastically different indexes on somewhat large databases (about 2TB altogether). This makes setting up replication a long process since I'd have to wait for the snapshot to insert + adding back all the unique indexes on the subscriber databases. That said, I'd like to avoid having to set this up from scratch again.
The problem I have is that the subscriber databases are now a part of an availability group. I've read where you can setup replication to use the listener name, but these guides always assume you're starting from scratch.
My question is: Is there a way to change the subscriber server name on the distributor and publishers to the new listener name so that replication will continue regardless of which replica is active? I've seen on the distribution database a table called MSsubscriber_info which indeed shows the instance name of the subscriber, but I really don't want to foul this up.
Thank you all for any assistance!
December 18, 2020 at 8:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
December 21, 2020 at 4:27 pm
Old Hand,
It is possible to use the listener name in a transactional replication environment that is using always on, perhaps you will need to re-create a replication suscriber and remove others, you will need to test with a suscriber that have very few articles or just one, I am attaching a link for you
Best regards
January 4, 2021 at 11:40 am
We can add the replication distribution database in the availability group for high availability starting from SQL Server 2017 CU6 and SQL Server 2016 SP2-CU3 It needs to set up using the scripts; We cannot use an existing Here, you can note that it shows the SQL Listener name for push subscriptions.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply