Dear All,

I want to set up snapshot replication on server that will serve as
Publisher and Distributor for minimum 40 Subcribers. The Subcribers
will receive a new snapshot each month.

I want to publish 3GB, and it's expected to grow.
I Want to minimize workload on the Publisher/Distributor.
What should I do??
- Should I Store in a shared folder on the file server or in an
alternative folder on the Publisher/Distributor??? Why?
-Which one should I used between pull subscription or push
subscription??? Why???

Thanks

Robert Lie

3 Gb is a lot of data to send of the wire each month. I'd look at
transactional replication is possible so the snapshot is sent once, and then
only the transactions. This will lessen the load on your server and your
network.

It doesn't really matter if you share it on a shared folder, alternate
folder or c:\temp (as long as there's enough room) for push.

For pull it has to be on a shared folder (like \\publishername\c$\Program
files\Microsoft SQL Server\MSSQL\ReplData) or an alternate share. The reason
you would wish to use an alternate share is so that the SQL Server account
on the subscriber does not have to be an admin account on the publisher. You
would want to do this in secure environments - it should be ok in your local
LAN/wan.

You would want to use push when 1) the number of subscribers are low 2) they
are well connected 3) you need a central point of administration or you want
to reduce your administrative over head (or you don't know about replication
monitor group)

You want to use pull when 1) you have a large number of subscribers -
typically over 50 but this depends on your hardware 2) they are not well
connected, you are replicating over the internet, or the subscribers will
set when they want to replicate 3) you can live without the central point of
administration

--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
[quoted text, click to view]