Have a look in BOL for
(1) merge replication and
(2) transactional replication with immediate updating
subscribers and
(3) transactional replication with queued updating
subscribers.
This is a bit simplistic, but in your case it sounds like
you're not on a LAN and need autonomy so I'd settle for
merge. One important point is that you'll need to
determine if the data on publisher and subscriber
overlaps or not - are conflicts possible or is the data
partitioned. If conflicts are possible, which algorithm
will be used for conflict resolution.
HTH,
Paul Ibison

(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Hello,

What requirements do i need to setup replication.

I have a sql server running at one location where the most updates occur and
another location where minimum updates occur (mostly read data requests).
The bandwith to connect each other is beneath 512kb.

Thnx