Post reply

Replication - missing records and large Msrepl_commands table

  • April 3, 2013 at 5:50 am

    #394514

    Hi

    We have run into a problem with missing data in our subscriber when using replication even though replication manager says its up to date. I noticed we did have an message in our subscriber saying Query Timeout exceeded, and some searching led me to look at the MSrepl_commands table in the distributor which has around 30million records in it.

    Since typing this the data has replicated now, however has anyone seen this before. Also is this amount of records in the MSrepl_commands normal?

    Thanks

  • April 3, 2013 at 8:38 am

    #1603208

    After reading some articles on retention periods for example here:

    http://www.mssqltips.com/sqlservertip/1823/troubleshooting-slow-sql-server-replication-issue-due-to-distributor-database-growth/

    Even though my subscriptions are set to never expire I don't believe this is impacting on my MSRepl_commands table. I tested it by changing to 336hours and running the job and nothing of note was removed. In fact I do not see how the publisher retention period has any impact on the MSRepl_commands table anyway.

    In any case I believe what has happened is that a query had a table lock which prevented the replication from working. Is this a likely scenario?

    Thanks

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply