Multiple Models in one SQL Server database

[areincke]

Hi,

we are using EA for quite a while now and have more than 100 eap files. To make working in our team easier we
decided to use a SQL Server for repository. Our company IT created a database for us on one of our central SQL Server.

But in the topic http://www.sparxsystems.com/forums/smf/index.php/topic,21106.msg185642.html#msg185642 I learned that we need one database for each of
our eap files to import in or we need to transfer all of our 100 files in one model. Now I am thinking about if working with one modell which holds this number of files is
not working well and asking our IT to create 100 databases on this SQL Server is not good eather.

So my question: Is there another way? Perhaps on another repository (not file based)?

Thanks for all input.

[Geert Bellekens]

You currently already have 100 databases, they are only in MS-Access format (.eap file) instead of SQL Server format.

If you want to keep a functional status quo (100 independent models) but still want to upgrade the technology then you'll have to create 100 database schemas in SQL Server. This is basically the same thing in any database format.

In general the preferred way of working is to work with a central repository for all of your models. (you can create multiple root nodes and treat each as a single "model")
The idea is that you can link and reuse across "models".
Only if you have hard constraints such as security concerns I would think about splitting up the models into different repositories.

Geert

[Glassboy]

Now I am thinking about if working with one modell which holds this number of files is
not working well and asking our IT to create 100 databases on this SQL Server is not good eather.

No, you could quite happily convert each of your eap files to a root node in a SQL database and it would work fine.  It might look a little messy but you could solve that by creating a content meta-model.

[Sunshine]

You can put all the 100 eap file models into one SQL repository. You just need to figure out how you want to structure it and that really depends on what you have in your eap files. If there is one for each project and the projects can be grouped into portfolios and programmes then it could look something like this
-Portfolio A (Root)
   - Programme A (View)
      + Project A (Package)
      + Project B (Package)
      + Project C (Package)
   -Programme B (View)
      + Project D (Package)
      + Project E (Package)
      + Project F (Package)
-Portfolio B (Root)
etc...

You can use XMI import/Export to create an XMI file from each eap file then import each one into the SQL central repository as structured above.
Hope that provides some food for thought.