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 »
Error Number: -1073548784 Executing the query “UPDATE STATISTICS [dbo].[***********] WITH FULLSCAN ” failed with the following error: “Could not allocate space for object ‘dbo.SORT temporary run storage: 142101814116352’ in database ‘tempdb’ because the ‘PRIMARY’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup,
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 »
When Replication the EXECUTION of a stored procedure to a subscriber select the “serialized transaction” and and wrap the SP execution within a transactions. This ensures the changes are replicated as a single stored procedure execution and not as individual row-level updates. See: Publishing Stored Procedure Execution in Transactional Replication “The serializable option is recommended
Read More »