Source Control w/Already Deployed Database

[gonzalo.vinas]

Hi there EA fellows,

         I've got to this situation recently at my work. There is a already deployed EA model into a DB Server without any source control mechanism at all.

The obvious idea is to get source control going ASAP. We have TFS. I've re-read the Source Control documentation and its pretty straightforward..  the thing I really don't get is once the model is uploaded into TFS.. what's the real need for the DB? -- Just model support the internal EA data model structure?

Thnks.

[HowardB]

Hello Gonzalo,

You are right, once your model is version controlled, it can be shared through the version control system, so the use of a third-party DBMS to store your model becomes less important.

Private Model deployment, (using .EAP files) combined with version control is quite a valid solution for team deployment of EA.

In previous releases of EA, our documentation has been somewhat unclear with regard to version control.  We have made some significant improvements over recent months.

Just to be sure that we are both talking about the same thing, please visit the following links to review the current information.

http://www.sparxsystems.com/uml_tool_guide/uml_model_management/applying_version_control_to_en.html

http://www.sparxsystems.com/uml_tool_guide/uml_model_management/applying_version_control_in_te.html


If you have any further queries, you can always email [email protected]


Best Regards,
Howard Britten

[Martin Terreni]

Well...it is all fine if you need to perform "get latest" to a couple of packages a day, but what if you have 10 poeple working on the model and then you have to perform it 20 times a day (or more). working with DB means that you don't need to perform it eveb once. you use VC for baselines, locking and restoring, not for charing the model.