EA Projects - encapsulate more than one project?

[cf]

Hi,

I do not know how EA was designed to be used:
it would be very comfortable for us to have one single EAP which includes several projects, which would be deployed on a sql-server database so everyone can access it.
My question is now: is one EAP meant to encapsulate more than one project? In some functionalities it would be not that good - for example "model tasks", ..., which are, as I think, only one per EAP.
But doing the whole SQL-Server-Installation for every tiny project would be really too much, besides you would not be able to browse the existing projects on the sql-server.

Has anyone an idea/experience with the working with a sql-server repository?

- thanks in advance

[potterm]

Cf,

EA supports multiple project root nodes within the same EAP file - i.e. place the analysis model for each project in a separate root node.  Each project is then browseable from the top level in the tree browser.

But as you say, some elements such as stereotypes, security settings, model tasks etc. would be common for all projects which is not ideal.  In particular, if you are using EA's security features you wouldn't be able to assign access permissions on a per project basis (AFAIK).

The only other way I know of is to create separate MS SQL databases, but again, as you say this is not ideal given the set-up work involved.

Martin.