Push vs Pull subscriptions

Hello,
I was wondering if there are any rules of thumb in
determining whether or not to use push vs pull
subscriptions?
Any help would be greatly appreciated!
Thanks in advance
Gene,
push will allow control by the publisher, while pull allows the subscriber
to control synchronization, so pull is often used for autonomous users - ie
users who may be disconnected.
It used to be the case that push would use the publisher/distributor's
resources, while pull used the subscriber's resources, but now there's the
posibility of remote agent activation so this distinction is not necessarily
true. However, it is still the case that whose resources are used may be a
consideration.
HTH,
Paul Ibison
|||migrate to pull when you start getting significant locking occuring in your
Distribution database.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uwTxIEeZEHA.3512@.TK2MSFTNGP12.phx.gbl...
> Gene,
> push will allow control by the publisher, while pull allows the subscriber
> to control synchronization, so pull is often used for autonomous users -
ie
> users who may be disconnected.
> It used to be the case that push would use the publisher/distributor's
> resources, while pull used the subscriber's resources, but now there's the
> posibility of remote agent activation so this distinction is not
necessarily
> true. However, it is still the case that whose resources are used may be a
> consideration.
> HTH,
> Paul Ibison
>
|||Hello
I have configured the PUSH server to be able to push
transactional mode and I cna actually configure the access
list. But when I go to the target server where the updates
are to be pushed to, I do not see the changes.
DO i actually have to create the Dbase first on the target
server?
also, on the target server, when I try to configure the
PULL subscription it is giving me access denied although
on the source/Publisher server, the target server was able
to be defined with no issues.
thanks

>--Original Message--
>migrate to pull when you start getting significant
locking occuring in your[vbcol=seagreen]
>Distribution database.
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
>"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
>news:uwTxIEeZEHA.3512@.TK2MSFTNGP12.phx.gbl...
allows the subscriber[vbcol=seagreen]
autonomous users -[vbcol=seagreen]
>ie
publisher/distributor's[vbcol=seagreen]
but now there's the[vbcol=seagreen]
distinction is not[vbcol=seagreen]
>necessarily
resources are used may be a
>
>.
>
|||Hello
I have configured the PUSH server to be able to push
transactional mode and I cna actually configure the access
list. But when I go to the target server where the updates
are to be pushed to, I do not see the changes.
DO i actually have to create the Dbase first on the target
server?
also, on the target server, when I try to configure the
PULL subscription it is giving me access denied although
on the source/Publisher server, the target server was able
to be defined with no issues.
thanks

>--Original Message--
>migrate to pull when you start getting significant
locking occuring in your[vbcol=seagreen]
>Distribution database.
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
>"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
>news:uwTxIEeZEHA.3512@.TK2MSFTNGP12.phx.gbl...
allows the subscriber[vbcol=seagreen]
autonomous users -[vbcol=seagreen]
>ie
publisher/distributor's[vbcol=seagreen]
but now there's the[vbcol=seagreen]
distinction is not[vbcol=seagreen]
>necessarily
resources are used may be a
>
>.
>
|||Yes,
You do need to set up the database on the target server
first. During initial syncronization, replication set up
will ask you if the subsribers have the latest data and
schema. If you say yes, the no snapshot synchronization
will occur, if you say No, a snapshot agent will run and
refresh the data and structure.
Regardless, you do need to have the target DB on the
target server.

>--Original Message--
>Hello
>I have configured the PUSH server to be able to push
>transactional mode and I cna actually configure the
access
>list. But when I go to the target server where the
updates
>are to be pushed to, I do not see the changes.
>DO i actually have to create the Dbase first on the
target
>server?
>also, on the target server, when I try to configure the
>PULL subscription it is giving me access denied although
>on the source/Publisher server, the target server was
able[vbcol=seagreen]
>to be defined with no issues.
>thanks
>
>locking occuring in your
message[vbcol=seagreen]
>allows the subscriber
>autonomous users -
>publisher/distributor's
resources,
>but now there's the
>distinction is not
>resources are used may be a
>.
>
|||Jeff,
when you create the subscription you specify the destination database, and
can create it at this stage, but it isn't created on the fly. During the
subscription set up, you have the choice to initialize or not. If the
destination tables (articles) exist and are identical to teh publishers then
you aren't necessarily required to initialize. Initialization will create a
snapshot of this data which can be BCPd into the destination tables, and
typically create them also. In your case you should reinitialize - force
replication to go through this process again. This will set up the
subscriber so replication can begin.
HTH,
Paul Ibison