Answered by:

Question

I'm uploading incremental data changes from SQL Compact 3.5 client to SQL Server 2008 w/change tracking enabled. It was recommended in the CTP2 documentation to use the SqlSyncProvider and SqlCeSyncProvider for this scenario.

I'm confused with the code sample listed because it uses the SqlSyncScopeProvisioning that when run adds additional change tracking tables, which seems redundant with internal SQL Server 2008 change tracking -- or are they complimentary of each other?

If the server using change tracking doesn't have to be provisioned, how do I configure the SqlSyncProvider and SqlCeSyncProvider to use SQL Server 2008 Change tracking?

Answers

Unfortunately, SqlSyncProvider does not support SQL Server integrated change tracking at this time. SqlSyncProvider requires the storage of additional metadata due to it's added capabilities such as the ability to sync between two clients as well as with the server. Instead, you should use a custom approach to change tracking and as you mentioned, we have made this a lot easier to do with the scope provisioning class insomuch that you just point it at the server and it adds all of the triggers and side-tables automatically. We are looking at adding integrated change tracking support in a subsequent release.

All replies

Unfortunately, SqlSyncProvider does not support SQL Server integrated change tracking at this time. SqlSyncProvider requires the storage of additional metadata due to it's added capabilities such as the ability to sync between two clients as well as with the server. Instead, you should use a custom approach to change tracking and as you mentioned, we have made this a lot easier to do with the scope provisioning class insomuch that you just point it at the server and it adds all of the triggers and side-tables automatically. We are looking at adding integrated change tracking support in a subsequent release.