2

I want to achieve below illustrated scenario via sql server replication.

enter image description here

Client A and Client B are client databases containing same article Table A. This article needs to be published by Client A and Client B whose changes need to be merged at the server (direction of arrows represent data flow).

Server is the destination database where article Table A should contain the changes made by both Client A and Client B. The trio consisting of Server, Client A and Client B are running Sql Server 2008 R2.

This is what I've tried in vain. Made Client A and Client B publishers and initially subscribed Server to Client A (went well). Next I tried subscribing Server to Client B (went haywire, found this msdn post where I figured out the reason behind the failure )

I still need to achieve the above diagrammed scenario. Is this even possible? If yes, any ideas how?

Thanks for your time.

2

Yes, this type of topology is known as the Central Subscriber Model. To make this work you should horizontally partition your published data, utilize static row filters, and set the Action if name is in use article property to Delete data. If article has a row filter, delete only data that matches the filter.

The MSDN article does not detail the implementation very well but I have covered it in Central Subscriber Model Explained.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy