Replication crashes on dump tran/dbcc checktable (syslogs)

I have running a replication mechanism using SQL6.5. It concerns about 15 user tables, grouped in several categories.

The replication is running alright and steady until the transaction log on the subscriber-database is dumped with DUMP TRAN <dbname> WITH NO_LOG, which is followed by DBCC CHECKTABLE (syslogs) to correct the number of pages assigned to syslogs.

Then the replication goes nuts, only to be recovered after installing the mechanism from the beginning.

I cannot leave the DBCC out, because this seems the only way of really emptying the syslogs table.

Martijn Rutte
OgilvyOne
Amsterdam
tinusAsked:
Who is Participating?
 
cymbolicConnect With a Mentor Commented:
Just a guess, but see if your subscriber database has the option Truncate Log on Checkpoint set on. This may substitute for a manual dump, and/or may be conflicting with your manual dump command (I know, it shouldn't matter, but you don't really believe that SQL server always works correctly, do you?).  Also, I noticed some fixes in Service Pack 2 for DBCC and replication.  Have you installed it?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.