KeithFranklin


Suppose your using Merge Replication.

2 Users in 2 locations issue updates to the same table. 1 updating 1 column and the other updating another column. Now in reality the actual Stored Procedure issuing the update statement is passed in all the possible columns that could change and builds an update statement that updates all columns even the ones that havent changed.

Will this break Merge Replications conflict tracking Or does SQL Server 2005 Merge Replication pickup that in reality the 2 updates only in reality changed the values in 2 columns.




Re: Does the actual update statement of a table affect Merge Replication?

Mahesh Dudgikar


Firstly, if you are using row level tracking, updates to different columns at 2 sites will result in a conflict.

Now, is this a user stored procedure that will do the updates to all columns If so, then yes, it will affect the conflict detection. From merge replication perspective, all columns are changed and it will flag it as a conflict.

Why do you need to update all the columns