none
Resuming last sync session RRS feed

  • Question

  • Is there any sample method to resume last interrupted sync session? Any help welcomes..
    • Moved by Wenchao Zeng Friday, April 29, 2011 6:23 AM SyncFx related question (From:SQL Azure)
    Thursday, April 28, 2011 11:27 AM

Answers

  • Hi,

    JuneT is right for the batching case when there is no further changes after previous failed sync. But if you have made further changes on the change enumeration database after previous failed sync, the old batching files will be replaced with new ones in the next sync because the previous batching files doesn't match the current database changes anymore.

    With SyncFx2.1, you also can consider enabling multi-transaction with ApplicationTransationSize especially when you work with SQL Azure databases (http://msdn.microsoft.com/en-us/library/ff928617(v=SQL.110).aspx). You may have less data integrity guarantee, but it allows sync to resume from the previous complete transaction of last failed sync.

    Thanks,

    Dong


    This posting is provided AS IS with no warranties, and confers no rights.
    Friday, April 29, 2011 5:05 PM
    Moderator

All replies

  • Hi,

    You want to resume from Data Sync Service? Or from your App built on SyncFx?

    Thanks,
    Dong


    This posting is provided AS IS with no warranties, and confers no rights.
    Thursday, April 28, 2011 10:52 PM
    Moderator
  • From app built on syncFx.
    Friday, April 29, 2011 4:48 AM
  • there is no special method to resume an interrupted sync. just fire off Synchronize again. however, if you have enabled batching, you may reduce the the need to re-download changes or re-enumerate changes on the server due to failed operations as Sync Fx can start from the batch where it failed.

    Friday, April 29, 2011 10:32 AM
    Moderator
  • Hi,

    JuneT is right for the batching case when there is no further changes after previous failed sync. But if you have made further changes on the change enumeration database after previous failed sync, the old batching files will be replaced with new ones in the next sync because the previous batching files doesn't match the current database changes anymore.

    With SyncFx2.1, you also can consider enabling multi-transaction with ApplicationTransationSize especially when you work with SQL Azure databases (http://msdn.microsoft.com/en-us/library/ff928617(v=SQL.110).aspx). You may have less data integrity guarantee, but it allows sync to resume from the previous complete transaction of last failed sync.

    Thanks,

    Dong


    This posting is provided AS IS with no warranties, and confers no rights.
    Friday, April 29, 2011 5:05 PM
    Moderator