February 2007 - Posts
In typical database to database sync scenarios where the backend database is SQL Server, the sync framework creates the schema for the tables undergoing synchronization on the client database. All that is needed is to have the SelectIncrementalInsertsCommand
Read More...
If you haven’t heard the news yet, SQL Server 2005 SP2 is out! Now if you are like me, thinking about data synchronization for the most part of your day, then you should be really excited about SP2. Let me tell you why. Recall that in all sync services
Read More...
If you had time to browse the documentation for Synchronization Services for ADO.NET , you might have seen a class called SyncAnchor. You don’t deal with it directly and none of the demos in my blog interact with it directly except the server command
Read More...
One of the important topics in data synchronization is managing metadata used to track changes on the store. Just a quick reminder of the different kinds of metadata used in the demos so far: Adding inline columns to each table we plan to synchronize.
Read More...
The long awaited for documentation and samples for the sync framework is out. I’ve to admit that I am amazed with the reaction and demand for more information for this new API. People seem to love it! Although the release of the CTP was rather quiet,
Read More...
It is about time for our offline application to deal with sync conflicts. Conflicts are fact of life in lazy synchronization environments. It is likely that your application users don’t want to deal with conflicts. Therefore you are encouraged to architect
Read More...
One of the common questions I get from developers once they get their hands on the new sync framework for ADO.NET is: How is it different from SQL Merge Replication? When should I use merge as oppose to sync services? Can sync services do filtering, ddl
Read More...
