In the procedure "xxxxxx_selectchanges", the value of @sync_min_timestamp is needed to determine if any changes can be picked up. For some unknown reasons,
this value sometimes jump to a big number, for
example "520402", which result in no changes be picked up. I re-provision the scope on client computer and start sync again. The value of
@sync_min_timestamp will be 0 at the first time, but will jump to "520402" at the second time.
Could you please advise how this value is determined and is there any way we can do a manual update of this value?
By the way, is this possible that we can decode the "scope_sync_knowledge", make some changes and save it back to the scope_info table?
Thanks!
JZ