Post reply

Deattaching a replicated subscription database

  • September 9, 2012 at 11:30 pm

    #263948

    hi,

    what is the best way of get rid of the log file from subscription database. it is growing big in production db. and i want to make it simple so that it'll not grow further.

    shall i deattach & attach again without log file so that a new log file will be created by sql server?

    is that a good practice?

    Thanks,

    Regards,

    Ami

  • September 10, 2012 at 3:36 am

    #1535580

    No. Don't do detach/attach. It's not a good practice.

    Are you taking the log backup regularly?

  • September 10, 2012 at 5:10 am

    #1535618

    thanks for your assitance,

    though it is a production db. we don;t take log back ups as it is dwhse.

    we have another db where one month of data will reside always and we can bring from it.

    even if it goes we can get the same from legacy systems.

    we take weekly once backup and other days incremental backup.,

    Regards,

    Ami

  • September 11, 2012 at 4:57 am

    #1536150

    You can change the database recovery model to "Simple".

    I believe now the database is in "Full" recovery model.

  • September 11, 2012 at 8:17 am

    #1536277

    Thanks.

    But how to get rid of current big log file?

    Regards,

    Ami

  • September 12, 2012 at 12:24 am

    #1536568

    Shrink the log file to appropriate size using DBCC SHRINKFILE command.

  • September 12, 2012 at 1:06 am

    #1536576

    can we do that in a subscripted replication database?

    will that affect replication?

  • September 12, 2012 at 3:18 am

    #1536611

    Yes. Log file of subscriber can be shrinked.

    It should not have any impact on replication.

  • September 12, 2012 at 4:30 am

    #1536636

    thanks!!

    Regards,

    Ami

Viewing 9 posts - 1 through 8 (of 8 total)

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