Merge Replication Conflict Detection vs Conflict Resolution Part 2: Custom Business Logic Handler

Attached is a sample Merge Conflict Handler sample I created.  I am including a walkthrough of the sample below.   1.  Create the sample merge publication/subscription databases Code Snippet:  From file  <1-CreatePub_Sub_DBs.sql>   2. Via management studio or TSQL scripts ( file 2-CreatePublication.sql) , create the merge publication ·         For Publication name specify: SamplePub1 ·        …


Merge Replication Conflict Detection v/s Conflict Resolution

One common misconception about how merge replication handles column-level tracking (detection) is that when a conflict is encountered, the winning row will include column values which did not conflict in addition to the "winning columns". For example: Originally Row100= col1=a, col2=b, col3=c, col4=d, col5=e User1 updates Row100: col1=f,    col2=g,    col3=h    — note: col4 and col5…