Replication prerequisites

I need to make use of replication to merge two remote databases with one
central database and then update the two remote databases with the data on
the central database. What is the prerequisites for setting up replication? I
want to use C# for the merging. What do I need to do, because I've been
confusing myself now with security issues etc, etc...
Please help anyone?
This sounds like merge replication, but could equally well be transactional
with queued updating or transactional with immediate updating subscribers.
Have a look in BOL for the differences between these methods, or if you post
back with details of the following, someone will be able to help out:
(a) are the publisher and subscribers continuously connected?
(b) does the data overlap? If so, will you need any complicated conflict
resolution methods?
(c) will there be other subscribers coming onboard?
(d) do all the tables have PKs?
(e) do you want to replicate the execution of stored procs?
As for the programming aspect, please have a look here for some details to
start off with:
The SQLDMO scripts on here: http://www.replicationanswers.com/Scripts.asp
The ActiveX control scripts on here:
http://support.microsoft.com/default...b;EN-US;319649
http://support.microsoft.com/default...b;EN-US;319646
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
Thanx alot for your response. I should be able to sort out the programming
side of this replication through some research that I have done. If you
wouldn't mind, I would like to go into more detail on what I want to do.
I have an application that our marketers will use to keep tract of their
leads and advertisers for our business directory website. Let's call the
marketers M1 and M2. ok, M1 and M2 will go out to different clients.
Obvisouly they won't go and see the same clients at the same time so they
need to share the information that M1 and M2 has gathered. So M1 has data and
M2 has a different set of data but they need to share it.
Both M1 and M2 are using laptops which isn't connected to our server or the
internet permanently. So M1 and M2 needs to come into the office and upload
their data and then receive new data that the marketer uploaded. If M1 came
into the office in the morning and uploaded his/hers data onto the server
using replication and M2 comes in, in the afternoon, M2 must be able to
receive the data that M1 uploaded that morning and then upload M2's data onto
the server so that M1 can receive M2's data the next time M1 uploads.
Hopefully that's explained clear enough to what I want to do. So, both M1
and M2 isn't always connected to each other or the internet. Yes, their will
be data overlaping since the server will have new information and the
marketer will also have new data which shouldn't be overwrittin but added.
All the tables have PK's. I don't have any stored procedures.
What will be the best option for this problem and how should I go about
setting everything up? I thought about having the each marketer's laptop as a
publisher and subscriber at the same time? is this possible?
Thanx again...
"Paul Ibison" wrote:

> This sounds like merge replication, but could equally well be transactional
> with queued updating or transactional with immediate updating subscribers.
> Have a look in BOL for the differences between these methods, or if you post
> back with details of the following, someone will be able to help out:
> (a) are the publisher and subscribers continuously connected?
> (b) does the data overlap? If so, will you need any complicated conflict
> resolution methods?
> (c) will there be other subscribers coming onboard?
> (d) do all the tables have PKs?
> (e) do you want to replicate the execution of stored procs?
> As for the programming aspect, please have a look here for some details to
> start off with:
> The SQLDMO scripts on here: http://www.replicationanswers.com/Scripts.asp
> The ActiveX control scripts on here:
> http://support.microsoft.com/default...b;EN-US;319649
> http://support.microsoft.com/default...b;EN-US;319646
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||If M1 and M2 connect up to a central server, I'd set up the central server
as a publisher with M1 and M2 as subscribers. I'd suggest looking at queued
updating subscribers for this scenario, provided you are not dealing with
text/image columns (merge would be the other alternative).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)