Post reply

Log File Size in the Distribution Database

  • April 26, 2006 at 3:35 pm

    #93729

    We have sql 2000 publisher/distributor pushing publications sql 7 subscriber.  The publised database at the subscriber has a big log file and is growing.  Can the recovery option be set to "Truncate Log on Checkpoint"?

     

    Thanks

    KR

  • April 28, 2006 at 12:55 pm

    #634986

    Yes.  As a matter of fact, the publisher and distributor can also both be set for SIMPLE recovery or Truncate Log on Checkpoint.

    Have Fun!
    Ronzo

  • April 28, 2006 at 7:07 pm

    #635030

    Well you can specify that option provide you can rely on your backup strategy

  • May 1, 2006 at 9:12 am

    #635137

    Well, we have currently backup happening every night on the subscriber.   The publisher backups are scheduled differently and it is in Full Recovery Module with full and transaction log back up happening periodically. 

    This is the strategy that is in place:

    In case the subscriber fails then the database would be restored/created using the Import/Export Tool and then the subscription would be recreated/reinitialized. 

    I am currently reviewing this and any input would be welcome.

     

    Thanks

    KR

  • May 2, 2006 at 10:34 am

    #635369

    Well can we see if ther are any kind of open transactions

    dbcc opentran('<database number>')

    and also select * from sysprocesses where blocked <> 0

    If there are any kind of open transactions the log reader agent tried to replicate the entries that are available.

    you can as well execute dbcc loginfo and see for any kind of active VLF's

    If none of the able work. What you can do is take a full backup and shrink the log file.

     

     

  • May 2, 2006 at 10:37 am

    #635372

    Thank you much for the info.

    KR

Viewing 6 posts - 1 through 5 (of 5 total)

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