Solved

Replication Subscriptions push  / pull

Posted on 2006-07-16
3
649 Views
Last Modified: 2009-07-29
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
Comment
Question by:TRACEYMARY
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 7

Author Comment

by:TRACEYMARY
ID: 17118902
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
 
LVL 28

Accepted Solution

by:
imran_fast earned 500 total points
ID: 17120274
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
 
LVL 7

Author Comment

by:TRACEYMARY
ID: 17123638
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

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Why is this different from all of the other step by step guides?  Because I make a living as a DBA and not as a writer and I lived through this experience. Defining the name: When I talk to people they say different names on this subject stuff l…
Load balancing is the method of dividing the total amount of work performed by one computer between two or more computers. Its aim is to get more work done in the same amount of time, ensuring that all the users get served faster.
Via a live example, show how to extract insert data into a SQL Server database table using the Import/Export option and Bulk Insert.
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function

617 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question