locked
SQL Provider sync framework: Select Changes returns no rows RRS feed

  • Question

  • Having re-provisioning our databases, we no long see our data syncing. running trace and looking through sql profiler, we see that all the calls to the various xxx_SelectChanges procedures set the Sync_min_timestamp parameter to 7FFFFFFFFFFFFFFF. A rather suspicious looking number to say the least. Of course nothing ever gets selected.  Moving the databases to our development systems work fine, but not on the production system.

    so, what could possibly cause this?  thank you-

    Friday, April 12, 2013 8:36 PM

All replies

  • have you used a backup of a provisioned database to initialize other clients?
    Saturday, April 13, 2013 1:46 PM
  • when we restored the DB's to another set of machines, they sync correctly. there is something about the environment of these other machines, but we are not sure where to look. we verified that the version of the sync runtime is the same on the machines that work and the ones that don't. 
    Monday, April 15, 2013 2:40 PM
  • so you provisioned a database, took a backup, restored on the client then synched?

    you should not do that. if you have provisioned the database before you took the backup, you should run PerformPostRestoreFixup after you restore it and before sync the restored copy the first time.

    Monday, April 15, 2013 2:43 PM