SQL Server Performance

Replication time-out w/ large TLog

Discussion in 'Performance Tuning for DBAs' started by hooperdba, Jan 23, 2007.

  1. hooperdba New Member

    Every sunday my reindex job runs and when it goes up against the largest
    table in db (90,000,000 rows) the reindex takes very long.. not sure exactly but the
    job which is around 20 reindex commands takes around six hours to complete.

    While this job is running my replication logreader times out and fails causing manual

    DB is 120GB
    TLog is 25GB

    Should the tlog be smaller. I've always read that Tlog should be sized around 1/4 the size of the db?

    Any ideas what to do about replication failure?

  2. satya Moderator

    The behaviour is by default due to the fact that reindex job is resource intensive job, during this time try to avoid running the replication update.

    Satya SKJ
    Microsoft SQL Server MVP
    Writer, Contributing Editor & Moderator
    This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
  3. MohammedU New Member

    Add your another schedule to run logreader agent to run every 10/30/60 minutes...so that it will start again itself other wise you have start it manually...

    By default schedule it start when sql agent is started if you configure the replication to run continuously...

    Mohammed U.

Share This Page