Risk of running Sync Framework without synchronizing Date and Time on client and server machines RRS feed

  • Question

  • We are running a hub and spoke network.  We store a master copy on the hub and synchronize data to/from local copies of the data on each spoke.  Data modification is relatively infrequent and it is rare that more than one spoke would reference the same records within a few seconds of an update from another spoke.

    It could be difficult to synchronize the date and time across all systems due to restrictions on internet access.  Also, the systems are not in a domain.

    What risk do we run by synchronizing the date and time within a few seconds or even a few minutes?

    Howard P. Weiss

    Thursday, September 25, 2014 6:01 PM

All replies

  • if you're using the newer sync providers,  it's based on timestamp, not date and time.
    Tuesday, September 30, 2014 4:57 AM
  • Please point me to an explanation of how timestamp is used to synchronize records in multiple databases.


    Howard P. Weiss

    Tuesday, September 30, 2014 2:08 PM
  • just check your _tracking tables and the _selectchanges SPs, you will find that they use the timestamp columns for storing the version and for selecting changes.
    Wednesday, October 1, 2014 6:56 AM