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)

  • September 16, 2014 at 12:11 pm

    #1745866

    dagnea (9/16/2014)

    ...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??

    Thanks,

    That does make sense. See: Considerations for Transactional Replication.

    Is that a bad thing? Provided that you have allocated enough space for your log, the subscriber is not down for too long and you're not dealing with millions of transactions not there should not be a problem. If you are dealing with a high volume of transactions then dropping and re-creating the subscription is probably the way to go. That is the approach I would take. Scripting out your entire replication setup is a nightmare but scripting out a subscription is not a big deal.

    "I cant stress enough the importance of switching from a sequential files mindset to set-based thinking. After you make the switch, you can spend your time tuning and optimizing your queries instead of maintaining lengthy, poor-performing code."

    -- Itzik Ben-Gan 2001