Replication between 2 publisher with same database

Hi,

Before this, I've 2 difference site that run SQL server 2000 as database server. One at north and the other at west.

At north, I've a group of terminal that run SQL server 2000. I've 1 main server that run as publisher and distributor to all the terminal. And also the main database is at the main server. The terminal will replicate together using merge replication. So that the data would be same at all terminal. At west it also have the same scenario.

Last week my boss ask me to replicate both main server ( north and west ). So that he want the data would be same at all place.

So, can anybody help me.....

hi

at first: a subscriber can also be a publisher!

but you have a problem: you have to reinitalize the replication from one point

for example: you publish the db from the west to the north, and there you have create the new subscription to the west-terminals

it is not possible to publish the db from one publisher to another publisher

summary

step 0: you have one publication with serveal subscriper (west)

step 1: create subscription to a server (north)

step 2: create there are publication

step 3: create subscription to other server

bye

thorsten ueberschaer

|||

Huh? Leave your replication implementation as it currently exists alone. Don't touch it, it's working just fine.

On your main server, create a new database which will combine everything together. Once created, push a subscription from North to this database. After that is done, push a second subscription from West to this database. (You have to configure the snapshot to leave the existing table intact otherwise it will error out when it tries to run the default option which is drop/create.

Before you combine these together, you have to make sure that you can actually combine the data sets in the same place. If you have the same primary key values on both the North and West servers, then you can't combine the data together. In this case, you can still bring it all into the same database, just not into the same set of tables.

BUT, there is no need to blow up your existing implementation just to meet this new requirement.