Post reply

Log Bloat when Performing Initial DB Push Using Transactional Replication

  • December 22, 2005 at 6:12 am

    #169939

    We have a 24 GB database we are replicating to a backup server.

    The partition on the backup server being used to hold the database is 60 GB with nothing else taking up space on the drive.

    The problem I am running in to is that the initial synchronization of the database is causing the log file on the subscriber to grow to such an extent the drive is running out of space, which in turn is causing replication to fail.

    Are there any strategies I could/should be using to minimize or manage log file growth during the inital sync?

    Any advice would be appreciated.

    Thanks.

  • December 26, 2005 at 8:00 am

    This was removed by the editor as SPAM

  • December 27, 2005 at 11:14 am

    #611579

    How are you pushing data to backup server to replicate?  Are you using DTS or inserts?  Log file will fill if you are using inserts or updates or deletes. DTS also uses inserts?  My advice will be to do in batches like 10,000 records at a time and keep backing up and truncating log file.

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

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