Multiple Models & SQL Server

[TheCosmicTrickster]

Can anyone tell me if it is possible to store multiple EA models in a single SQL Server database?

We have several .EAP files that we want to migrate into a SQL Server-based repository.  However, it appears that you need one database per .EAP file (the documentation is not very clear on this point).

[skiwi]

Yes we do in an SQL Server based repository,
both created in the repository, and imported from previous .eap files.

[Paolo F Cantoni]

Yes we do in an SQL Server based repository,
both created in the repository, and imported from previous .EAP files.

I think we need to be careful about terms here...

A single MS SQL Server instance can hold multiple EA repositories (each one a SQL Server DB) each of which can hold multiple models (EA Package Roots).

Each .EAP file (An MS Access DB with a different file extension) is also a repository which can hold multiple models.

There are a number of mechanisms to transfer model data from a .EAP repository to a MSSQL repository.  The easiest, Tools|Data Management...|Project Transfer..., will clone one repository into another, "blowing away" the target.

So, if you started with 3 .EAP DBs; using this mechanism you would end up with 3 corresponding clone MSSQL DBs.

If, however, you want to aggregate multiple models (EA Root Packages) from multiple .EAP repositories into a single MSSQL repository, you need to use a different mechanism:  XMI package transput - output from one repository,input to the other.

Trickster, can you specify which scenario is the one you need?

HTH,
PAolo

[son-of-sargasso]

transput

Wow, I thought for a moment you may have been too far into the Margaret River's of late.

Thank goodness for google though. http://en.wikipedia.org/wiki/ALGOL_68#transput:_Input_and_output


   (s'Friday, forgive me.)

[Paolo F Cantoni]

transput

Wow, I thought for a moment you may have been too far into the Margaret River's of late.

Thank goodness for google though. http://en.wikipedia.org/wiki/ALGOL_68#transput:_Input_and_output

   (s'Friday, forgive me.)

ALGOL68!   That brings back fond memories!

I actually wrote an in memory dynamic database in Algol68 at what used to be Caulfield Tech (in Melbourne).  You defined the model in what today we'd call a DSL and then entered the instances...

The first language that actually expanded my programing horizons...

I thought, I wrote, it did - minimal semantic gap!

The best non-OO language, in my opinion.  Much underrated - typically by people who'd never used it!

Thanks for reviving the memory!
Paolo

[TheCosmicTrickster]

Yes we do in an SQL Server based repository,
both created in the repository, and imported from previous .EAP files.

I think we need to be careful about terms here...

A single MS SQL Server instance can hold multiple EA repositories (each one a SQL Server DB) each of which can hold multiple models (EA Package Roots).

Each .EAP file (An MS Access DB with a different file extension) is also a repository which can hold multiple models.

There are a number of mechanisms to transfer model data from a .EAP repository to a MSSQL repository.  The easiest, Tools|Data Management...|Project Transfer..., will clone one repository into another, "blowing away" the target.

So, if you started with 3 .EAP DBs; using this mechanism you would end up with 3 corresponding clone MSSQL DBs.

If, however, you want to aggregate multiple models (EA Root Packages) from multiple .EAP repositories into a single MSSQL repository, you need to use a different mechanism:  XMI package transput - output from one repository,input to the other.

Trickster, can you specify which scenario is the one you need?

HTH,
PAolo

We're aiming for the second one - multiple EAP repositories into a single MSSQL repository.  I'll get the user to experiment with XMI, see if he can get what we want.

Thanks for the help.

CT