restarting subscriber node in transactional replication

  • Hi,

    In my business our  current replication topology is as follows. We have our Production node(Publisher), and our subscriber node. The subscriber is also where the distribution db is hosted.

    We are using transactional replication and I have a couple of queries. If we need to restart or stop the subscriber node I'm under the assumption that I need to stop the log reader agent and that's all.

    Once I bring the subscriber node back up, baring there are no schema changes at the publisher (prod), will enabling the log reader agent bring my subscriber back up to date, or will I need to generate a new snapshots?

     

    Oh and the agents on the subscriber are pull

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

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

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