SQL Server Repository question

[Rick]

Newbie question here. I've been using EA Corporate edition for some time now, but we have just decided to use SQL Server as a repository for our projects. It appears that we need to create a new database for each project. Is that correct? That would seem to proliferate a lot of databases. It is also going to be a pain as our DBAs don't like the idea of everyone on the team being able to create databases. Does anyone have any suggestions as to how one might organize models to minimize database sprawl?

[«Midnight»]

Hi Rick,

Yes, that - your assumption about one database per project - is correct.

There's not much you can do to limit this. The best thing you can do is work out some kind of modus vivendi with your DBA group. Consider using a shared Access (an EAP file) to get project a project going, to the point where you know a shared repository will actually be useful. While this is going on start the necessary conversations with the appropriate DBA contact to work out where the repository will reside (should it prove necessary), who the users will be, and the necessary access rights.

You should also work with your database group to establish standard usernames and roles for accessing EA repositories. These can go a long way towards reducing the front-end overhead involved in starting a new project.

David

PS: Others will certainly have more useful suggestions about this matter. You might want to set the Notify option to keep you informed when this thread is updated.

[Rick]

David,

Thanks for the confirmation. I've already begun discussion with our DBA group to simplify the process along the lines you suggested. I was just hoping that I had overlooked or misunderstood something before investing time in figuring out how to deal with the design of the product.

Rick

BTW - I have turned on notification.