• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 670
  • Last Modified:

Replication Subscriptions push / pull

I was testing out replication from scratch.
Managed to created the publication.

I ended up with two subscriptions one PULL and One PUSH
One i did with tools and one i did by right clicking on the replication publication create...and doing push.

Whats the difference with PUSH and PULL...

Im only going from ONE database to another and not make changes at all on the PUBLISHER.

Thanks
0
TRACEYMARY
Asked:
TRACEYMARY
  • 2
1 Solution
 
TRACEYMARYAuthor Commented:
I just read

Push subscription is subscription when the publishing server will periodically push transactions out to the subscribing server or database.

Pull subscription is subscription when the subscribing server will periodically connect to the distribution database and pull information.

The Distribution database is a system database, which is stored on the Distributor and does not contain any user tables. This database is used to store snapshot jobs and all transactions waiting to be distributed to Subscribers.

So does that mean..
PUSH             (will not store the transactions in distribution but just do the replication transactions at the subscriber)
and
PULL (All transactions go to distribution first then subscriber gets them)

Would the PUSH be quicker in this sense.......( or by putting transactions in distribution take load of main database)

Thanks
0
 
imran_fastCommented:
Hi,
In both case the replicated data will be stored at the distribution.

Push subscribtion
Push subscriptions can simplify and centralize subscription administration because you do not need to administer each Subscriber individually. The Distribution Agent or Merge Agent runs at the Distributor when synchronizing a push subscription. Push subscriptions are created at the Publisher, and the replication agents propagate data and updates to a Subscriber without a request from the Subscriber. Changes can also be pushed to Subscribers on a scheduled basis.
Use push subscriptions when:
Data will typically be synchronized on demand or on a frequently recurring schedule.
Publications require near real-time movement of data without polling.
The higher processor overhead at a Publisher using a local Distributor does not affect performance.
You need easier administration from a centralized location (the Distributor).

Pull Subscriptions
Pull subscriptions are created at the Subscriber, and the Subscriber requests data and updates made at the Publisher. Pull subscriptions allow the user at the Subscriber to determine when the data changes are synchronized, which can be on demand or scheduled.
Use pull subscriptions when:
Administration of the subscription will take place at the Subscriber.
The publication has a large number of Subscribers (for example, Subscribers using the Internet), and when it would be too resource-intensive to run all the agents at one site or all at the Distributor.
Subscribers are autonomous, disconnected, and/or mobile. Subscribers will determine when they will connect to the Publisher/Distributor and synchronize changes.
0
 
TRACEYMARYAuthor Commented:
Thats a lot to take it.......

Im trying to take the distribution which we have on SQL1 and put this on SQL2 so the overhead is on SQL2
But the data will be taking from SQL1 so when i set up replication i going to say the distribution is on the
SQL2.....................

So i use pull ? right now we are using PUSH...

Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now