Home Forums SQL Server 2005 SS2K5 Replication How do I handle transactional replication when moving the Subscriber (shutdown for a day and bring online) RE: How do I handle transactional replication when moving the Subscriber (shutdown for a day and bring online)

  • dagnea (9/16/2014)


    his reasoning, he insisted that the log file on the publishing database will not get truncated and will grow until the stopped subscription is started and the subscriber synched.

    Does this make sense??

    None at all.

    If were taking down the distributor, then yes, the log would grow. You're not. You're moving one of the subscribers. The publisher won't even notice because it doesn't care whether or not there are any subscribers at all, if they're up, down or anything else

    Transactional replication is publisher -> distributor then distributor -> subscriber.

    Providing the period that the subscriber will be disconnected is less than the retention period for the replication, when the subscriber is reconnected it will catch up. If it's disconnected for longer then the subscription will be invalidated and will need to be re-snapshotted.

    So, no. There's no grounds for the sysadmin's concerns. Providing the distributor is up and the log reader running, the log on the publisher will be properly truncated at the usual points.

    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