migrating data when version upgrade

Post Reply
wgoebl
Posts: 20
Joined: 09 Dec 2011, 11:08

Hi,
How much effort is it to upgrade data entered in Versoon X of Essential Project to Version X+1? Which Tasks must be performed? Thx Wolfgang
User avatar
neil.walsh
Posts: 444
Joined: 16 Feb 2009, 13:45
Contact:

Hi Wolfgang,

Typically, we provide separate upgrade scripts for version upgrades. Currently, these are run from the script tab within Protege though we're working on simplifying this even more. This current method isn't complex but can be prone to "user error" or typos so we thought we'd trying and make it even more simple.

An example of the current upgrade process can be found here...
http://www.enterprise-architecture.org/ ... l-Patch-1/

Major versions would follow a similar technical process. You would need to upgrade each repository individually. In terms of other tasks, backing up your existing repositories prior to upgrade is always very important (though I expect you do this regularly anyway). If customisations have been made to the meta model (either extensions or changes) then these need to be carefully reviewed prior to upgrading. We'd always advise creating test repositories to review the impact of any upgrades prior to rolling them out to production repositories. Commercial support is always available to help you with any upgrades too through the project sponsors, EAS, though in most cases you wouldn't need this.

We have a major meta-model release due shortly however the upgrade script will likely be released shortly afterwards. Creating the migration scripts is resource intensive for us and we take extra care to get these right. Users could use the period of time between releases to get familiar with the changes and prepare for the upgrade.

Hope this answers your question.

Cheers

Neil
Post Reply