What happens when a sync is broken... (Sync Framework v1 - via Designer) RRS feed

  • Question

  • Here's the scenario -- we have guys out in the field that do not sync fully because they will lose connectivity over air cards, etc.  Their sync is for large amounts of data some download only and some bidirectional.  Much of the sync was written in the designer.  So what exactly happens if they are in the middle of syncing, say, their inventory, and they lose their connection.  Are half the changes applied and the change tracking assumed updated?

    The problem is that some users never get all their changes (downloads only even) after they sync.  My theory was that they may be having their connection broken in the middle of the sync process which was somehow screwing up their database at which point the database would assume change tracking/anchor was up to date.  If not, what else might cause this?  Any ideas are appreciated.

    Tuesday, May 11, 2010 2:16 PM


  • Hello Travich -

    Using Sync Framework V1, the change application transaction commit is on the sync group level.  In another word, if a sync is interruptted on one sync group, the changes should be bailed out.  In general, we recommend putting all related tables in one sync group during the design time.

    When your users observed that they did not get changes, did they miss all changes or just a part of it?   We should never have partial data applied on the sync group level.  Werer all tables put in the same sync group?


    Leo Zhou ------ This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, May 11, 2010 5:23 PM