About: ReplTalk

5 thoughts on “Troubleshooting LogReader Timeout executing sp_replcmds”

  1. Can you explain the impact of a timeout?  Are the replicated transactions lost (to the distributor and any subscribers)?

  2. The Distribution Agent will apply a "batch" of changes in a single transaction.  If the Agent fails it will rollback any partial changes that were part of that "batch". If the Agent is scheduled to restart, it will again timeout and again rollback changes.  You'll be caught in an endless loop.

    When you increase the timeout value, then rerun the Agent those changes will be reapplied to the Subscriber.  You can also temporarily decrease the BatchSize to commit a smaller batch of transactions.

  3. Hi, I am new to the concept of replication. Can you please tell me how to change the Query timeout parameter?

  4. You can also add a new profile in the Log Reader Agent Profiles and already in this new profile increase Logintimeout and Querytimeout.  In my case it's worked.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.