If a SQL Server Replication Distributor and Subscriber are on the same server, should a PUSH or PULL subsciption be used?
Posted
by
userx
on Server Fault
See other posts from Server Fault
or by userx
Published on 2013-10-18T20:07:05Z
Indexed on
2013/10/18
21:58 UTC
Read the original article
Hit count: 179
Thanks in advance for any help.
I'm setting up a new Microsoft SQL Server replication and I have the Distributor and Subscriber running on the same server. The Publisher is on a remote server (as it is a production database and MS recommends that for high volumes, the Distributor should be remote).
I don't know much about the inner workings of PUSH vs PULL subscriptions, but my gut tells me that a PUSH subscription would be less resource intensive because (1) the Distributor is already remote, so this shouldn't negatively effect the Publisher and (2) pushing the transactions from the Distributor to the Subscriber is more efficient than the Subscriber polling the Distribution database.
Does any one have any resources or insight into PUSH vs PULL which would recommend one over the other? Is there really going to be that big of a difference in performance / reliability / security?
© Server Fault or respective owner
