locked
how to update value of @sync_min_timestamp? RRS feed

  • Question

  • 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


    • Edited by jz2012 Wednesday, June 12, 2013 2:40 PM
    Wednesday, June 12, 2013 1:52 PM

Answers

  • that timestamp is not autoincrementing number, thats based on the timestamps it has received from synching. if the timestamp values of the source replica are already high, then it will be high. 

    is the source a restored database?

    you can always serialize the sync knowledge as xml, but i wouldnt suggest you mess up with it.

    • Marked as answer by jz2012 Thursday, June 13, 2013 11:28 AM
    Thursday, June 13, 2013 12:43 AM