Projects and Databases

[hjs51]

I am a new EA customer. I am just starting to use the product and I got the corporate edition for its ability to save data in a database.

On that issue I would like to get guidance from those with exprerience.

Question: Should the relationship between a database and a project be a one to one relationship?

I can think of many instances where I might want to reuse objects I created in one project in another project and therefore think it might be wise to store all such data in a single database.  

But, I don't know whether EA Architect has a mechanism for isolating one project from another in a common data store.

[peter.zrnko]

One project = One schema in a database.
You can have many projects in one database. These projects will be stored in different schemas.

Projects stored in different schemas are completely independent.
If you want to share parts of your projects, consider export/import package(s) via XMI or version cotrolled packages (these options are nearly the same because a package is internaly exported in XMI format before storing in CVS).

[larsgk]

I work on a large-scale project (actually a series of software projects). All of our projects share the same model repository database, which makes it easy to share model elements between projects.
We have structured the model by creating one root node per project. Each root node (project) has the same set of views (Logical, Component, Deployment) at its top level.

[Graham_Moir]

Yes root node is the key.  Once you have your database and associated connections set up then creating root nodes in the project browser effectively gives you a portfolio of projects in the same database.

[«Midnight»]

It certainly works, and EA is designed to handle this gracefully.

There will still be limits on linking (for example) from one model to another. Look through the last 6 months or so of the forum for some lively discussions.

Just another 0.02 CAD.

David