Post reply

Bloated log file after configuring Transactional Replication in SQL Server 2005

  • July 29, 2011 at 7:53 am

    #245141

    My database size is 80GB, after configuring transactional replication on my production database the log file size became 100 GB from 1.3 GB. Could this have happened because my subscriber is not yet online and initial snapshot has not been replicated to the subscriber? After replicating to the subscriber will my log file be back to the normal size? Are there any specific database settings that need to be changed before configuring replication?

    Thanks,

    Sridhar.

  • July 29, 2011 at 8:04 am

    #1360827

    Is the log reader running?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • July 29, 2011 at 8:15 am

    #1360831

    Yes, the log reader agent is running.

  • July 29, 2011 at 8:22 am

    #1360837

    Then work through this:

    http://www.sqlservercentral.com/articles/Transaction+Log/72488/

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 4 posts - 1 through 4 (of 4 total)

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