locked
How to abort sync properly RRS feed

  • Question

  • Wondering how to abort sync that is taking too much time properly. Aborting a thread seems too drastic since it might leave some parts of DB in incosistent state.

    Any suggestions?

    • Moved by Hengzhe Li Friday, April 22, 2011 7:54 AM (From:SyncFx - Microsoft Sync Framework Database Providers [ReadOnly])
    Thursday, October 9, 2008 7:35 AM

All replies

  • Unfortunately there is no abort functionality available.

    Consider moving the sync to a background thread if its a long running one.

    Friday, October 10, 2008 5:43 PM
    Moderator
  • It is running in a background thread. But while it is tables that are being synced at that moment are locked from being changed. So obviously running it for a long time is not always a good solution. So sometimes it's necessary to abort sync.

    Friday, October 10, 2008 5:50 PM
  • Hmm. Well killing the background thread programatically is probably your best solution for the timebeing. All sync changes obliviously happens within a transaction so it should not affect your database state if you abort it. I will pass this feedback to our team so we can start thinking about supporting abort in the next release of Microsoft sync framework.

    Friday, October 10, 2008 7:58 PM
    Moderator
  • Hi Maheshwar,

    I'm sitting with the same issue as the original poster. Have you had any feedback from the team regarding the Abort() feature?

    Another question, when aborting the background thread during a sync operation, will the transaction be aborted on the SQL CE side immediately and all locks released, or will the transaction have to go through a timeout period before the locks are released?

    Beyers
    Tuesday, November 11, 2008 1:41 AM