Change Tracking fixes in SQL 2014 SP4 CU4

ReplTalk ReplTalk Blog August 7, 2019

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 »

not been designated as a valid Publisher

ReplTalk Troubleshooting July 18, 2019

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 »

New Merge subscriber fails with sp_MSsetconflicttable

ReplTalk Inside Replication July 17, 2019

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 »

SSMS 18.1 Replication Monitor missing support for Always On

ReplTalk Product Updates, ReplTalk Blog July 16, 2019

With SQL Server Management Studio 17.7 release, Replication + Always On technology was fully supported allowing registration\connections via Always On Listeners. This update fully supported use of Tracer Tokens following failover to a secondary Replica. https://docs.microsoft.com/en-us/sql/ssms/release-notes-ssms?view=sql-server-2017#download-ssms-177 What’s new Replication Monitor: Replication monitor now supports registering a listener for scenarios where publisher database and/or distributor database
Read More »

How to skip a transaction

ReplTalk ReplTalk Blog, Troubleshooting May 28, 2019

Stored procedure sp_setsubscriptionxactseqno allows Distribution Agent to skip transaction(s) in Transactional Replication. Internally this stored procedure sets the last delivered watermark (LSN) stored in subscriber’s MSreplication_subscriptions table. Upon restarting the Distribution Agent return transactions greater that this watermark (LSN) from the Distribution database cache (msrepl_commands). [crayon-5e4db9d0e9e5d538648557/] Skipping Errors Skipping Errors is useful when Distribution Agent is
Read More »