SQL Database per Model

[kimballjohnson]

Am I correct in understanding that EA requires one DBMS database per model?

That is, I should run the enterprise db script on one new database per *.eap file?

Thanks,

Kimball

[«Midnight»]

Yes Kimball, you are, sort of...

I think that what you are asking is whether you require one database per EA project. The answer is yes.

However, EA considers the root package at the top of a project (the thing that owns the EA "Views") to be a "model." You can create new (additional) root packages if you so desire. EA will treat each as a separate UML model (at the highest level) with Views, package trees, etc. all its own.

There are various reasons you might want to do this, and there are several good reasons why you might not. All of this depends on your corporate or personal approach to UML, as well as any methodology you might engage; as with many other facets, the framers of UML left the possibility for practitioners to use or not as we saw fit.

If this leaves you up in the air, the gurus on this forum have some pretty good advice, and I'm sure they will weigh in if and when you ask.

HTH, David

[kimballjohnson]

Hmm...

Sounds like one of those areas I should stay out of until I have a situation that can't be done some other way.

But I think for now one database per project is meaningful.

Thanks!

[thomaskilian]

Kimball,
as David stated you are right and wrong. You can use either method and each has pros and cons. Single Repos: things can get mixed up but you have easy access to some kind of common repository; only one glossary; only one Model Tasks; etc. Multiple Repos: yes - vice versa. So it depends what you favour. You might need to go kinda mix of both. This topic has also been discussed several times here (sorry - sometimes I get tired searching the keywords again ).

You have to gain your own experience in order to find the right way.