SQL Server Profiler showing 9003 Exception when CDC is configured

While troubleshooting a customers environment I encountered the following 9003 Exception error message captured in SQL Server Profiler. “The log scan number (42:358:1) passed to log scan in database ‘<db name>’ is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this…

0

Troubleshooting LogReader Timeout executing sp_replcmds

Chris Skorlinski Microsoft SQL Server Escalation Services SQL Server Transaction LogReader Agent timeout executing sp_replcmds occurs most often when a large transactions has been written to the Published database transaction log, or there are a large number of un-replicated commands.  Either problem requires the LogReader to read more log entries than the timeout parameter allows…

5

Published Database Transaction Log continues to Grow!

Chris Skorlinski Microsoft SQL Server Escalation Services 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’)…

1