Pull or push subscription?

Faustino,
I agree about pull, and you might also want to
investigate a remote distributor to offload production
server processing, especially if you are using
transactional replication.
HTH,
Paul Ibison
The problem with pull subscriptions is that you no longer have a central
point of administration.
What this means is that if a pull subscription agent fails you will not see
the error on your publisher, but will have to visit the subscriber to see
this error. To get around this use replication monitor group and add all the
subscribers to it.
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:3ec801c48ff9$11379320$a601280a@.phx.gbl...
> Faustino,
> I agree about pull, and you might also want to
> investigate a remote distributor to offload production
> server processing, especially if you are using
> transactional replication.
> HTH,
> Paul Ibison
|||Actually we are planning to do a merge replication with all sites. It is the
database for an order processing system. Each branch will be feeding us with
the orders and we will sent them price changes etc.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:3ec801c48ff9$11379320$a601280a@.phx.gbl...
> Faustino,
> I agree about pull, and you might also want to
> investigate a remote distributor to offload production
> server processing, especially if you are using
> transactional replication.
> HTH,
> Paul Ibison