UPDATE: 4/10/2020 The steps below walk through setting SQL Server 2016 Replication Publisher, Distributor, and Subscriber each in an Always On Availability Group with one set of replicas residing one 1 subnet and 2nd set on another subnet simulating 2 different data centers (Pub1, Dist1, Sub2) <–> (Pub2, Dist2, Sub2). More Information: Configure replication with
Read More »
Currently Microsoft SQL Server Always Distributed Availability Groups does not support one global listener for the entire distributed AG. Replication in an Availability Group is currently is configured using a single Listener. Until either Distributed AGs support a single Listener or Replication support multiple Listeners, Distributed AG and Replication environments are not compatible. As improvements
Read More »
You may have the need to customize the stored procedures used by the Distribution Agent to apply changes to the Subscriber. For example, if in your particular environment replicated DELETEs often fails with “Row not found” error, by now you’ve most likely change the Distribution Agent to use the “Continue on Errors” Profile or added
Read More »
The Cumulative Update 4 for SQL 2014 SP3 contains these important fixes for Change Tracking technology. Cumulative Update Package 4 for SQL Server 2014 SP3 – KB4500181 https://www.microsoft.com/en-us/download/details.aspx?id=57663 FIX: Tlog grows quickly when you run auto cleanup procedure in SQL Server 2014, 2016 and 2017 https://support.microsoft.com/en-us/help/4500403/fix-tlog-grows-quickly-when-you-run-auto-cleanup-procedure-in-sql-serv FIX: Syscommittab cleanup causes a lock escalation that will
Read More »
Today while walking customer through Replication + Always On combination we encountered various errors like Msg 14080, Level 11, State 1, Procedure sp_MSvalidate_distpublisher, Line 17 [Batch Start Line 0] The remote server “SQL502” does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
Read More »
I’ve not seen this problem for year, but it came up again today. We were following the steps to setup a Merge subscriber using Backup\Restore from the Publisher. The database was very large, no filtering, two subscribers, each with complete match set of data from the publisher. Backup\Restore works great, saves time pushing down individual
Read More »