How to resolve primary Key changes with Sync Framework 2.1

Typically you do not change primary keys. I would expect to see instead the creation of a new row with updated key and deletion of old row. That will sync properly to remove the slave copy of the old row while adding the new one. I guess you can do this in a INSTEAD OF UPDATE trigger that processes as normal unless the following condition is true UPDATE(PK) then you would insert a new row into your database with the new PK and other values of row and delete the original row versus updating.

The issue with UPDATE is it will come over to the slave and try to match on the PK to do update. Since the PK is now changed, you won't make any connections.

Kevin

I have a restriction and i can't create triggers appart from the ones created by the sync framework provisioning. I thought maybe the sync framework could be configured to track the PK changes too.

How would it match to the row to change the PK? If you have other columns that act as additional unique (natural) keys, then you may be able to JOIN on those update PK ...

I guess Sync Framework works different because it's able to detect and apply a DELETE. i just tested and manually deleting and inserting the row worked. But I would highly prefer the framework to work with the updates.

The framework should work for updates, just not against the primary key. Sorry.

The was no solution I had to change my environment

@mentor360: so to be clear for future readers - sync'ing primary key changes will not work, so your workaround is to make the column you needed to be able to change NOT a primary key. Anyway, glad you got this sorted.

Best regards and happy coding,

Kevin