views:

28

answers:

2

I have 2 similar tables in different servers, data in certain columns can only be changed by server A while data in other columns can only be changed by server B.

However, I need these tables to always be consistent (1 minute schedule). Is this the kind of scenario that "Transactional replication with updatable subscriptions" solves?

+2  A: 

You want merge replication.

Joe Stefanelli
In this case, which server should I set as the Publisher? Or does it not really matter?
Eton B.
Obviously, I don't know all the specifics of your set up, but if both nodes are equally available, then the choice is arbitrary.
Joe Stefanelli
Thanks! Just what I needed.
Eton B.
+2  A: 

YEs, updateable subscriptions allow for this, but that is a deprecated feature:

This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.

The way going forward is Peer-to-Peer Replication.

Remus Rusanu
I'm reading this is a 2008 Enterprise feature, but thanks for letting me know the updatable subscriptions is deprecated !
Eton B.
From the link you provided, "We strongly recommend that write operations for each row be performed at only [one] node". I interpreted the OP as needing to update different columns of the same row at both nodes.
Joe Stefanelli
@Joe Stefanelli: true. Why I refrain from recommending Merge is because the underlying infrastructure for Merge is Triggers based and I found it not very scalable in real life. Transactional puts a much lighter load on the system, being log read based.
Remus Rusanu