Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: Guillaume on June 25, 2015, 07:11:03 pm

Title: Migrating EA project to a new DBMS
Post by: Guillaume on June 25, 2015, 07:11:03 pm
Hi,

I need to move a very large EA project currently shared via a DBMS to a different DB server.

I wonder if there's a better option between the following:
1- Data Transfer DBMS to EAP, and transfer EAP to the new DBMS schema (this has been tried and prompted a duplicate Index error, perhaps due to a Jet Engine limitation)
2- Data Transfer DBMS to DBMS (from the old to the new schema) -> this seems reasonable provided both servers are accessible from the same PC
3- use the DBMS backup/restore (e.g. MySQL dump), no EA required.

thanks
Title: Re: Migrating EA project to a new DBMS
Post by: Geert Bellekens on June 25, 2015, 07:25:36 pm
Quote
Hi,

I need to move a very large EA project currently shared via a DBMS to a different DB server.

I wonder if there's a better option between the following:
1- Data Transfer DBMS to EAP, and transfer EAP to the new DBMS schema (this has been tried and prompted a duplicate Index error, perhaps due to a Jet Engine limitation)
2- Data Transfer DBMS to DBMS (from the old to the new schema) -> this seems reasonable provided both servers are accessible from the same PC
3- use the DBMS backup/restore (e.g. MySQL dump), no EA required.

thanks
In order of preference: 3, 2, 1

The duplicate index issue might be resolved with a project integrity check.

Geert
Title: Re: Migrating EA project to a new DBMS
Post by: Guillaume on June 25, 2015, 07:29:30 pm
Thanks for your input Geert.  :)
Title: Re: Migrating EA project to a new DBMS
Post by: Guillaume on June 30, 2015, 11:19:26 pm
We used option 3 (DB bak & restore) to transfer our EA project.
We ran a project integrity check which prompts around 30 results as follows:

xxx - Invalid package object. ITEM: xxxxx. ACTION: Delete Invalid Package Objects.

I'm surprised that EA suggests that a model package must be deleted to "clean" the project. Will it really delete this package or just "clean it" from a DB perspective?

Thanks,
Title: Re: Migrating EA project to a new DBMS
Post by: qwerty on July 01, 2015, 03:33:07 am
It's save. Don't let EA get you confused about its intention.

q.
Title: Re: Migrating EA project to a new DBMS
Post by: Guillaume on July 01, 2015, 05:23:36 pm
thanks for your input