This project has moved and is read-only. For the latest updates, please go here.

Data migration strategies

Oct 24, 2013 at 2:41 PM
In the project I'm currently working on, we are using ManagedEsent and PersistentDictionary. One of the concerns recently has been how we should handle migration when the model objects in the application changes.

When we look at the data when using PersistentDictionary, the version number of the DLL is stored in the blob data. Can we have a reasonable migration solution and still use PersistentDictionary? If so - how do people do it?

If we move away from PersistentDIctionary and use the ManagedEsent API directly, how do people migrate data when there is a need for changing the model? Any pointers on how to do this?