Started a new thread as my original was out of control.
Quick description of problem..

We have had a server in LocationA for quite some time. The need arose
recently to have a server setup in LocationB due to the bandwidth in
location B is not wide enough to allow a direct access to LocationA's
server.

I have read a lot of posts and webistes, but still am semi in the dark.
About the only thing i've figured out (i think) is that I will need to do
some sort of merge replicaiton.

Paul asked the following questions...

[quoted text, click to view]

Yes.

[quoted text, click to view]

Yes. Both have an initial snapshot of the same data. The table that will
be updated on both the most often is the reports table. But in general
both servers need to have the same data all the time.

[quoted text, click to view]

Yes, both are always connected.

[quoted text, click to view]

I need the data from server B at least once a night, however the more often
the better, but lets focus on once a night for now.


[quoted text, click to view]

Lucas,
I would recommend merge replication with queued updating. There is limited
support for conflict resolution ie not a big choice of resolvers, and you
can't update BLOBS on the subscriber. Provided these are not problems, it
would be much faster than merge replication.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)