Posted by yashgt on 08/21/07 12:19

We have a simple problem:
We have a table Assets[asset_id, title] and a table
Asset_Versions[asset_id, version_no]. In addition, there are columns
added by replication for storing the ROWGUID.
After synchronzation, assume both Node1 and Node2 have
Assets(1,'XYZ') and Assets_Versions(1,1)

Before syncing again a new version is added at both nodes so that both
Node1 and Node2 have
Assets(1,'XYZ') and Assets_Versions(1,1)(1,2)

Now when it syncs again, the publisher will make another entry of
Assets_Versions(1,2) in the subscriber thus disturbing the business
logic because the Subscriber will now have 2 entries for version_no=2.

How can we make Replication identify this as a conflict. Can we write
a conflict resolver for such a situation so that we can choose the
entry that was made last and make it the winner?

Thanks and regards,
Yash

• Next in forum: Re: MS SQL dealing with duplicate columns in rows?
• Prev in forum: Re: MS SQL copy new and modified rows from TABLE1 to TABLE2
• Thread view: Merge replication: How to avoid duplicates of records?

[Reply to this message]