none
Manually updating last sync timestamp

    Question

  • When we know 2 databases have the same content (we inserted the data by the same sql-script) is there a way to update the last sync timestamp in the metadata (scope_info) to simulate we have already synchronized all the data. In that way not all data is again synchronized during the next synchronization.
    Wednesday, July 24, 2013 4:02 PM

All replies

  • it's the knowledge columns in the scope_info table that's used during synchronization. 

    if you want to initialize databases with same data, provision one database, back up, restore, performpostrestore fixup then sync.

    or you can use SQLCe to generate a snapshot.

    Thursday, July 25, 2013 2:29 AM
    Moderator
  • For the initial installation we already use the backup/restore/postrestore. But when we change the schema, create a new scope to replace the old scope, we don't want all the data again transmitted to all clients (talking about a few thousands clients and tables with more than a million records). We know all databases are in sync, but still all data is again transmitted for the new scope. Then we would like to set a value in the scope_info (hack) to let the sync framework know they are already in sync.
    Thursday, July 25, 2013 6:47 AM
  • for new scopes, your sync knowledge is empty. the only way it gets populated is via sync.

    in the past, i would create a utility app that does a sync, but on changesselected event, remove all rows from the dataset, thus sending nothing. 

    Friday, July 26, 2013 3:31 AM
    Moderator