locked
All rows uploaded on subsequent sync with no changes for bidirectional tables RRS feed

  • Question

  • We have an application running under .NET 4.0 using SQL Server CE 3.5 SP2, and Sync Framework 2.0. For the initial synchronization, the entire sync process is completed on the server, and then the .SDF file is downloaded to the client. When the client does the first subsequent sync, before making any changes at all, every single row for all tables that are bidirectional gets uploaded to the server. Syncs after this are fine. Looking at the data, it seems the framework has changed the __sysTrackingContext on these rows for these tables.

    Any ideas as to what is going on here?


    DRM

    Thursday, July 19, 2012 1:24 PM

All replies

  • is the sync created using the Local Database Cache wizard? if yes, are you using SQL Change Tracking or Custom tracking?

    Thursday, July 19, 2012 2:06 PM
  • No wizard. The same code is executed for initial syncs and subsequent sync. For initials, the local database is generated on the server, and then streamed to the client. The process is still invoked by the client. On the server we are using custom tracking. This only started happening when we upgraded to .NET 4.0, SQL CE 3.5SP2, and sync framework 2.0.


    DRM

    Thursday, July 19, 2012 2:10 PM
  • am assuming the versions of SQL CE and Sync Fx on both client and server are the same?

     try checking the anchor values in __sysSyncArticles or __syncArticles and see if its getting reset to null... 

    i remember a similar thread but i think that one is for a WM device. 

    Thursday, July 19, 2012 2:24 PM