“The row was not found at the Subscriber when applying the replicated command.” errors reported by the SQL Replication Distribution Agent can often be some of the hardest issues to troubleshoot. With great satisfaction I was able to uncover this mysterious error for one of my customers. In the customers SQL Replication topology they’re consolidating
Read More »
Just wanted to give a heads up about a SQL Replication Distribution Agent Latency problem we observed today. The Distribution Agent to 1 subscriber was only delivering about 500 cmds/sec while other subscribers were getting 4000 cmds/sec. We noticed the Distribution Agent was running under a different PacketSize, made that change, no noticeable improvement. While
Read More »
A customer recently noticed their Published database transaction log would continue to grow until they backed up the Distribution database. DBCC OPENTRAN() Oldest distributed LSN : (0:0:0) Oldest non-distributed LSN : (982:100898:1) --> 0x000003D6 : 00018A22 : 001 -- Commit Tran(sp_replshowcmds) 0x000003D6:00018A22:0004 select [Current LSN],[Operation],[Transaction ID], Left([Description],20) from::fn_dblog('0x000003D6:00018A22:001','0x000003D6:00018A22:0004') “… to clear out the Transaction Log
Read More »
The scripts below and the video capture walkthrough setting up a Microsoft SQL Server Replication Distributor using SQL commands. As discussed in previous posting, the Distributor is a key role in Replication. It serves as a “cache” holding transactions for Transactional Replication and history tracking for all types of Replication. I’ve highlighted some of the
Read More »