locked
What is SyncDirection.Snapshot? RRS feed

  • Question

  • What is SyncDirection.Snapshot and how it is used?
    • Moved by Max Wang_1983 Friday, April 22, 2011 11:22 PM forum consolidation (From:SyncFx - Microsoft Sync Framework Database Providers [ReadOnly])
    Thursday, February 1, 2007 3:07 PM

Answers

  • The other SyncDirection options (UploadOnly, DownloadOnly, Bidirectional) involve tracking changes on the client, the server, or both. SyncDirection.Snapshot allows you to refresh the complete data set on the client, without change tracking. Each time you sync, the data at the client is overwritten for the tables where you specify SyncDirection.Snapshot. This can be useful in the following scenarios:

    • Data changes infrequently.
    • It is acceptable to have copies of data that are out of date with respect to the server for a period of time.
    • You are synchronizing small volumes of data.
    • Many changes occur over a short period of time, so it's cheaper to refresh periodically rather than track and deliver individual changes.

    Michael Blythe
    Programmer Writer
    Data Replication and Synchronization

    ==================================================

    Thursday, February 1, 2007 6:16 PM
  • In addition to the reasons Michael mentioned, Snapshot doesn't require any change tracking meta data on the server.  So, if you're synchronizing a table that you can't add a LastEdit type column to because you can't make schema changes, you can still synchronize data with the Snapshot option.

     

    Steve

    Tuesday, February 6, 2007 3:05 AM

All replies

  • The other SyncDirection options (UploadOnly, DownloadOnly, Bidirectional) involve tracking changes on the client, the server, or both. SyncDirection.Snapshot allows you to refresh the complete data set on the client, without change tracking. Each time you sync, the data at the client is overwritten for the tables where you specify SyncDirection.Snapshot. This can be useful in the following scenarios:

    • Data changes infrequently.
    • It is acceptable to have copies of data that are out of date with respect to the server for a period of time.
    • You are synchronizing small volumes of data.
    • Many changes occur over a short period of time, so it's cheaper to refresh periodically rather than track and deliver individual changes.

    Michael Blythe
    Programmer Writer
    Data Replication and Synchronization

    ==================================================

    Thursday, February 1, 2007 6:16 PM
  • Thank You.
    Friday, February 2, 2007 12:51 PM
  • In addition to the reasons Michael mentioned, Snapshot doesn't require any change tracking meta data on the server.  So, if you're synchronizing a table that you can't add a LastEdit type column to because you can't make schema changes, you can still synchronize data with the Snapshot option.

     

    Steve

    Tuesday, February 6, 2007 3:05 AM