Below are cause and recommendation for the SQL Replication LogReader error “The specified LSN (…) for repldone log scan occurs before the current start of replication in the log (…).’. When the LogReader starts, it verifies the Last Distributed transaction (last transaction in msrepl_transactions) still exists in the transaction log. This confirms the Published database
Read More »
Any Cox | Microsoft Premier Field Engineer We recently encounter the a problem where Replication Distribution Agent failed with error below while trying to replicate the “execution” of a stored procedure. Msg 0, Level 20, State 0, Line 0 A severe error occurred on the current command. The results, if any, should be discarded. Executing
Read More »
Problem Customer observes high latency in SQL Server 2005 Merge replication. In sysprocesses you see that Merge agents are being blocked by another Merge agent & the blocker Merge agent SPID is sleeping with “AWAITING COMMAND”. Root Cause If you take output of “select open_transaction_count from sys.dm_exec_requests where session_id = <blocker SPID>” & find that
Read More »
Anurag Sharma | Microsoft SQL Server Escalation Services Background In many cases customer often have large databases published and creating a snapshot of such large database is always a pain. And, even when published databases are of manageable size, a slow or unreliable network link can further complicate the issue. From SQL Server 2005 onwards
Read More »
Here are some thoughts on using Transactional (or Peer-2-Peer) Replication Subscriber to support both REPORTING and DISATER RECOVERY. Normally “subscriber” target server would have different set of non-clustered indexes to support REPORTING capabilities. The Publisher’s indexes, check-constraints, triggers, etc, would only be added when Publisher goes down and the Subscriber comes online as the new
Read More »