Is it possible to have only client side columns for bi-directional database synchronization when using a database cache?

When you are create a database cache and want to do bi-directional synchronization I have read that you should use GUID's as a key instead of a unique Id to prevent clashes during synchronization. There will be a performance hit though so is this a required trade off when using synchronization?

As well it looks like you need to have colum开发者_如何学运维ns added to your tables on the server (ie. creationdate and lastedited date) in order to enable bi-directional syncing. I will not be able to do this so is it possible to do this with these columns in the client side database only? I do not understand why they HAVE to be on the server.

you are not required to use GUIDs. it's only advised when you're using identity columns which can lead to duplicate values when you upload to the server unless you've partitioned your identity key values between clients and servers such that the identity values dont overlap.

am assuming you're referring to using the Local Database Cache wizard to generate the sync code, the datetime columns are for change tracking. It's there so sync framework knows what has changed in the server. If you cant add columns to the table, then use Sql Change Tracking.