Category: Troubleshooting

The process could not execute ‘sp_replcmds’

Share this PostSQL Server Transaction LogReader Agent timeout executing sp_replcmds occurs most often when a large transaction(s) are written to the Published database transaction log, or 100s of millions of un-replicated commands from logged index maintenance or changes to replicated tables.  Either problem requires the LogReader to read more log entries than the timeout parameter
Read More »

“Replication Monitor could not insert the tracer token”

Share this PostI’m seeing an uptick in customers using combination of AlwaysOn and Transactional Replication. Some are configuring the Publisher for high-availability, and some are configuring the Subscriber with Read-Only Secondary to prevent contention from the Distribution Agent updates and “reporting” read queries. Once configured, Tracer Tokens are often used to monitor end-to-end Transactional Replication
Read More »

KB article 312292 How to enable replication agents for logging to output files in SQL Server

Share this PostWhile troubleshooting SQL Server Replication we often want to capture detail step-by-step execution of Replication Agent.  One technique is to configure the Agent to log its execution to a Text file.  This posting walks through a couple of different ways to accomplish this.  It is also covered in the KB article http://support.microsoft.com/?id=312292.  I’ll
Read More »