Book a Demo

Author Topic: SQL Server 2000 & Corporate Edition  (Read 4353 times)

alarsen

  • EA User
  • **
  • Posts: 23
  • Karma: +0/-0
  • EA Rules!
    • View Profile
SQL Server 2000 & Corporate Edition
« on: July 07, 2004, 10:03:44 am »
Setting up SQL Server and EA was no problem.  My question is: Do I have to set up a separate database for each project.  It appears you do.  I kept loading in projects with the transfer option until I realized I was overwriting the previous project with each transfer.  At work I've been given access to one database for my development work.  Our DBA assigns and sets up the databases for us.   ???

thomaskilian

  • Guest
Re: SQL Server 2000 & Corporate Edition
« Reply #1 on: July 07, 2004, 11:07:01 am »
In general you are right that each project requires a separate database. You could place different projects inside the same db using different views. However, this is not a very good compromise since you have only one glossary, requirements table a.s.o. Try soothing your dba to allow more than one db - the size will be very small.

Bruno.Cossi

  • EA User
  • **
  • Posts: 803
  • Karma: +0/-0
    • View Profile
Re: SQL Server 2000 & Corporate Edition
« Reply #2 on: July 07, 2004, 02:10:04 pm »
Just as a workaround, you can also create multiple schemas within the SQL Server database that you have, and create an EA repository in each of the schemas.

Bruno