Unexplained slowness in SQL 2008 on Windows 2008 R2

Chris Skorlinski Microsoft SQL Server Escalation Services A customer called today about an unexplained slowness in SQL Server 2008 on Windows 2008 R2.  All SQL data looked great, no blocking, no obvious IO bottlenecks, just overall slow performance. 976700  An application stops responding, experiences low performance, or experiences high privileged CPU usage if many large…

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

Determine Transactional Replication workload to help resolve data latency

Chris Skorlinski Microsoft SQL Server Escalation Services Latency problems are often caused when series of transactions are trying to move a large batch of commands from the Publisher to the Distributor to the Subscribers.  The queries below show overall rows counts and index statistics for commands stored in the Distribution database. Use the results of…

0