This is a very detail article on how the merge replication works, thanks Sebastian.
I have merge replication setup in 2 servers running SQL Server 2016 and now I'm struggling with the conflict detection level, the column-level tracking is not working as expected.
Let's say I have the table name Employee with a few columns, I tested the column-level tracking as below:
Publisher: issue update command: "Update Employee SET FullName = 'abc' WHERE EmployeeID = 1"
Subscriber: issue update command: "Update Employee SET Remark = 'def' WHERE EmployeeID = 1"
I updated the same row but different columns from the publisher and subscriber, base on the definition of column-level tracking, this scenario is not considered as conflict and both update from the publisher and subscriber will take effect, but my publication always see this as the conflict and auto resolve by treating the publisher as the winner.
Did I mis-understand how the column-level tracking working or did I miss something in the configuration steps? I already reinitialize the subscriber and create new snapshot also.
Thanks in advance.