Holger Linke Microsoft SQL Server Escalation Services Abstract: This article describes an issue with SQL Server Transactional Replication that was detected recently. If you have configured the Log Reader agent to use the MaxCmdsInTran parameter, and also have configured the Distribution database to use the “sync with backup” option, you may experience a failure of
Read More »
Abstract Many technology solutions use a STORE and FORWARD model to move data though out the business. It begins when source data change is detected, collected, and STORED in a cache. This cache data, often on a schedule, is processed and FORWARD to one or more destinations. Microsoft technologies using “store and forward” include Log
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 »
Anurag Sharma | Microsoft SQL Server Escalation Services Log Reader fails with below error message The process could not execute ‘sp_repldone/sp_replcounters’ on ‘SQLGUY’. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011) Get help: http://help/MSSQL_REPL20011 The log scan number (23:49:3) passed to log scan in database ‘PUBLISHER’ is not valid. This error may indicate data corruption or that the
Read More »