April 22, 2018 at 8:58 pm
We have a request to configure transnational replication on AlwaysOn Availability Group with 3-4 replica nodes of different SQL servers.Have you seen any issues with configuring replication on top of AAG? Worried about performance impact and was thinking about doing a poc but I am not sure how I could proof the overhead. Any advise please? Many Thanks.
April 23, 2018 at 5:08 am
It's been a few years for me since I saw this, but you may wish to consider using trace flag 1448:
Enables the replication log reader to move forward even if the async secondaries have not acknowledged the reception of a change. Even with this trace flag enabled the log reader always waits for the sync secondaries. The log reader will not go beyond the min ack of the sync secondaries. This trace flag applies to the instance of SQL Server, not just an availability group, an availability database, or a log reader instance. Takes effect immediately without a restart. This trace flag can be activated ahead of time or when an async secondary fails. For more information, see this Microsoft Support article.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply