Post reply

Log file growing becuase Replication has been stopped?

  • March 13, 2008 at 12:57 pm

    #103471

    I started up Replication about 4 months ago.

    Last Sunday it started to Timeout, after serveral attempts to get it going, I just stopped it.

    Our data base is 250GB+, but we are only replicating 15 of the 200 tables.

    I'm guessing that since I only stop the log reader that the log file is going to keep growing until I have a chance to delete the replication?

  • March 16, 2008 at 8:45 pm

    #790183

    Log reader agent stopped working, so the published data in the transaction log will not be sent/marked as being read. They remain in the transaction log.

    You may need to use sp_repldone to clean the log. Check books online first (Caution).

  • March 17, 2008 at 8:36 am

    #790376

    Thanks for your reply.

    I used a script to delete the Replication process and then I was able to shrink the log file back down to size.

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

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