November 19, 2015 at 12:58 pm
Hi all,
We're about to setup our first Windows Cluster with Always On Availability Groups, and I have some questions regarding Replication. What is the suggested or tried and true way to keep the Distributor fault tolerant since it can't be added to a Replica? Is it suggested to put the Distributor in a traditional Always On Cluster instead?
Also with this would it be better to replicate to the Always On Cluster instead of a database on an Always On Availability Group? I'm still new to replication with AG, so I'm not sure what pitfalls come with this though I have worked with replication on Clustering. I guess I'm just trying to iron out the pro's and con's of moving the databases we replicate with to a SQL 2014 Cluster or to the Availability Group.
Thanks for any insight or thoughts.
November 20, 2015 at 3:31 am
there are a number of articles on MSDN, these two offer further information
https://msdn.microsoft.com/en-us/library/hh710046.aspx
https://msdn.microsoft.com/en-GB/library/hh882436.aspx
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 7, 2015 at 7:12 am
I have just configured this very thing. I have installed the distributor on a separate standard FCI. The TechNet articles/BOL are very good on this subject.
A few tips:
1. Make sure that the publications are the same on all AG replicas and use the same accounts throughout.
2. Make sure to configure the redirect on the distribution database to your listener name:
USE distribution;
GO
EXEC sys.sp_redirect_publisher
@original_publisher = 'MyPublisher',
@publisher_db = 'MyPublishedDB',
@redirected_publisher = 'MyAGListenerName';
3. Test it fully before deployment 🙂
This is a good article.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply