Page History

Modified Timestamps cannot be used to detect deleted rows, since the row is no longer available to be detected via a timestamp. As such, this approach is not suitable where the removal of a row is used to indicate loss of eligibility. There are several alternatives:

1. Change the inbound SQL view to use valid_through to indicate loss of eligibility, instead of removing the row.
2. Occasionally run Sync Job with theforce=1 option to process all rows, which will include deletes. This might be suitable for smaller data sets, or where it is acceptable to check for deletes less often than adds/updates.
3. Use Archive Tables instead, described below.