Don’t let change pass you by! Get started with Change Tracking in your SQL Database | Data Exposed

[@DB-sf1hy]

Very good idea to also include topics about features that are not new.

[@gaberice4365]

Thank you, good explanation and examples. I use it to track changes in my organisation where a third party data mart app provides incremental updates to one of our DBs.

[@CarlintVeld]

This seems to be very useful for an online data migration where one continuously replicates the changes across the wire until the cut over moment. What would be the most efficient way to obtain the changed data? Maybe CDC would be a better match?

[@Astral100]

Also it looks like there is a bug in Change tracking. Updating same row with several updates keeps the same (single) SYS_CHANGE_VERSION for all of the updates, even if you run updates separately! Which makes it impossible to trigger processing for only that one column that has just been updated.

[@Astral100]

Thank you, that was very helpful. Finally allowed me to understand what I was doing wrong in following examples on Microsoft learning pages. (This damned 'ColumnId', which is a string constant, unlike the other parameters in the COLUMNPROPERTY, ugh...)

[@glennaitchison2527]

Wish they went through it slower