SQLServer Replication, dealing with updating data in a subscriber without merging with the publisher

Posted by FlySwat on Stack Overflow See other posts from Stack Overflow or by FlySwat
Published on 2010-05-05T02:03:30Z Indexed on 2010/05/05 2:08 UTC
Read the original article Hit count: 353

Filed under:
|

To simplify my problem, picture two databases, one is a publisher, one is a replicated subscriber.

Most of the time, changes are configured in the publisher, and pushed to the subscriber once per day using transactional replication. (The subscriber is the main production database).

However, on a rare occasion, we need to make a change directly to the subscriber database. This does not break replication, however to ensure consistency, we also want to replicate this single change back to the publisher database.

My first thought was to make both databases publishers to each other, but that does not work. Merge replication also does not work as that merges the data together, and we really only want to push that single change from the subscriber back to the publisher.

Is there some other replication scheme I can use here, or do I need to invent my own thing?

© Stack Overflow or respective owner

Related posts about SQLServer

Related posts about replication