Sync Framework Considerations for Smart Client app -
With Microsoft Sync Framework SQL 2005? Is this possible? It seems that OTB providers use the SQL2008 functionality I'm looking for some quick win in relation to a sync project. The client application will be offline for several days. It will be a central server that should be SQL Server 2005. I 3.5 I can use. Client app originally can go offline for one week. When it comes back online, its data needs to be synchronized. But the good thing is that the data needs to be taken only on the server. The stuff that sinks back to the customer will be the lookup data that the client can never change. So this means that I do not care about sync conflicts.
To make the scenario easier for you, this smart customer remains offline and the user surveys data about some comments. They enter the data in the system. When the laptop reconnects to the network, it syncs back all the data on the server. Other clients are doing the same thing, but no one can ever touch each other's data then some reports have been seen on the server to see the data on the server. This also needs to be used on clickon.
My biggest concern is that the client is offline, while there is an interim release. This release may require a new field in the database, and a new area to fill in the survey. Obviously the new area will be negligible because we can not update old data, it's OK to set it as a notion. But when the client connects and its local data schema and server schema do not match, will it handle the handle of the framework? After pushing the data to the server, it is discarded locally.
Hope my problem is understandable.
I am using a Microsoft Sync Framework for an application that is to deal with conflicts, and This is a sad * .sdf file locked for some schema changes (like leaving a column, etc.).
Your scenario looks like the sync framework will work out of the box for you ... just make the problems in these examples from the Don Sync Framework, because any referenced integrity can not be implemented.
As far as you update the schema, if you follow the Sync Framework Forum, you are instructed to create a temporary table that the table should look at the end, copy your data, And then leave the old table once you have done the work, go ahead and rename the new table and re-add it to the SQL Server CE so that you can handle the sync class.
IMHO, I'm going to be working on removing sync functionality from my app because it has more prevention with a help.
Comments
Post a Comment