1

I have Transactional Replication set up with a Remote Distributor and a Pull Subscription. So as I understand it, at one end I have the Publisher, and at the other end I have the Distributor, Log Reader Agent and Subscriber. Therefore, all activity is initiated from the Subscriber end. The Log Reader Agent monitors the Publisher, and the Distribution Agent monitors the Distribution database at the Distributor.

Given this architecture, why during the configuration stage does the Publisher need to be able to connect to the Subscriber / Distributor? If the Subscriber / Distributor server can "see" the Publisher, why isn't this enough, as it seems all activity is initiated at the Subscriber / Distributor end?

Improve this question

1 Answer 1

Reset to default
1

I believe whenever transactional replication is initialized, the Publisher snapshots the articles in the publication and pushes it across to the subscriber. The remote Distributor and pull subscriber are used for the transactions after replication has been setup and initialized.

Improve this answer
1
  • Interesting. I thought the snapshot agent at the remote distributor controlled both the generation of snapshots at the publisher, and pulling the snapshot across to the subscriber. Struggling to find documentation on this.
    – Ronnie
    Jul 12, 2016 at 16:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.