Replication design

Hi,
I'm new to MSSQL replication, and was hoping for some advice as to
recommended practices for my scenario.
I will have a 4 SQL server scenario at four locations connected through a
TCP/IP wan (i.e. each site is connected to the internet).
One of the sites is the headquarters site. Some tables are only updated
at the headquarter, and these changes should replicate to the other sites.
For example the table that contains the list of all products is only updated
at the main site.
Each site (including the headquarter) inserts many transactions within the
day. I wish for all the transactions to replicate to all sites. For
example, if I insert a transaction at site A, I want this transaction to
replicate to site B, site C, and headquarters as well. The same goes for
all sites. Ideally this should happen within an hour from when the
transaction was entered.
The databases will be about 10-15GB each I think.
Any comments or suggestions appreciated,
Edgard
Edgard,
for those tables which are only updated at HO, I'd recommend transactional
replication.
For all other tables I'd recommend merge.
One hour's latency should not be a problem, provided you have the necessary
bandwidth and the amount of changes is not too great.
Regards,
Paul Ibison