Question about SQL Repositories

[SAB]

I have recently upgraded EA to the corporate version, one of the items that I am interested in working with is storing my model information in SQL Server. I have successfully transfered data for a model from and EAP file to the SQL repository, and when looking to transfer another model, I noticed that EA wants a separate DB for each repository.

When discussing this with my DBA, I needed a crowbar to remove his hands from my neck.  Apparently having a different DB for each of our models is not something that he is very interested in.

I am looking for 2 things from he collective, 1) is my understanding of having separate DB's correct; and 2) if not, how do you put multiple models into one DB; and I guess 3) do we like this?

[Paolo F Cantoni]

Hi SAB,

You should think of it in terms of Repositories and branches.

Each EA Repository, whether Server or Direct File based can hold multiple branches.

The Tools|Data Management|Project Transfer... functionality (incorrectly named) transfers entire Repositories.  So you can copy only one repository up to the Server.

However, you can export an entire repository as an XML and import it - at a different level.

My recommendation is to create a new (empty) EAP file and create only one "project" in it called Repository.  Then export both existing models and import them below the Repository  node.  Then you can transfer this new repository up to the Server replacing the one that's there...

HTH,
Paolo

[SAB]

Thank you Paolo, That will definitely give us something to consider.

[AndyJ]

My recommendation is to create a new (empty) EAP file and create only one "project" in it called Repository.  Then export both existing models and import them below the Repository  node.  Then you can transfer this new repository up to the Server replacing the one that's there...

Paulo, if you checking multiple projects in and out of this single repository, does EA manage to keep your project glossaries intact, or do you end up with a single mish-mash of all of your projects?

[Paolo F Cantoni]

Paulo, if you checking multiple projects in and out of this single repository, does EA manage to keep your project glossaries intact, or do you end up with a single mish-mash of all of your projects?

I believe there's only one Glossary per Repository.  So it's a mash-up.

However, there might be ways to structure things so that it's not so much a problem...

I think it's a case of "You pays your money, you takes your choice"...

I'm of the view that a single Glossary per (anything) is flawed anyway.  In my experience Glossaries are much more context sensitive than is initially apparent.  I'm looking at other solutions.

Paolo