Microsoft Sync Framework with Mutliple Client and Server Database

Question

I am working on changes to the application to have a local data store, and not directly connect to the database server. The client application then synchronizes the changes between the two server databases and the local data warehouse. I am trying to implement a synchronization solution using Microsoft Sync Framework. To be clear, there is no server application, only a database server, but there are several clients.

I started to implement two classes that implement FullEnumerationSimpleSyncProvider, one of which is called LocalSyncProvider, and the other is ServerSyncProvider. LocalSyncProvider knows how to list, insert, update, delete items from the local data store, and ServerSyncProvider knows how to list, insert, update, and delete items from the database server. Each of them uses the provided SqlMetadataStore and stores two metadata repositories (one for the local and one for the server) on the client’s local disk. This means that each client will have its own metadata store for its local data store and its own metadata store for the server database.

Will this work, do I need only one server metadata repository, or do I need to use the synchronization structure in different ways?

Answer 1

We use a similar approach, and it works as you described. The difference is that we synchronize files, not data, using the FileSyncProviderclient and the implementation FullEnumerationSimpleSyncProviderfor the server. But we do not have Sync Framework code running on the server, and there are two separate metadata files that are stored on the client.

, , , . , , , , Sync Framework , /, .