sql server replication: Hi,

We are planning to replicate our bussiness database on some of our branches
for reducing response times for these sites. Branches will merge it contents
at night with our central database, just to avoid the overload of our main
server at day. We are planning to deploy around a dozen of subscribers. I
think the apropriate subscription for the remote sites is Pull subscription,
despite all branches have permanent connection to the headquartes, in order
to avoid the publisher overload. What do you think about it?
Any suggestion is welcomed

--
Faustino Dina
--------------------------------------------------------
If my email address starts with two 'f'
drop the first 'f' when mailing me.

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,

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


[quoted text, click to view]

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.

[quoted text, click to view]