Version Control and Database Repository

[mac1929]

We're developing a project using EA 5.0. So far, we have been using a database as a project repository, and have not used version control.

Now we need to control changes to our model so I've configured EA to use CVS, and it works fine.

In our new situation, should we use a file repository instead of a database one??. We needed that database to share models among project members, but now CVS can do that work, and also a file respository is slightly faster than the database one.

Is there any benefit in using a database in our situation? Any hint will be welcome. Thanks!!

[Paolo F Cantoni]

It really depends on your exact usage.  But here's some figures that might help.

I had a decent conceptual model in Rose it used to take over 30secs to open the model.  Under EA it takes less than 7.  Other models would take close to a minute to open under Rose, I suspect (since we haven't moved them to EA) they might take about 10 secs to open.

One of the principle decisions in my coming to EA was it was repository based.  I can make changes directly into the database and even simulate some functionality EA doesn't yet provide by direct access to the DB.

HTH,
Paolo

[TrtnJohn]

It may depend on the size of your model.  The file repository is really just an Access database.  So the question is will Access be faster than your DB repository when the model grows larger?  

[thomaskilian]

It may depend on the size of your model.  The file repository is really just an Access database.  So the question is will Access be faster than your DB repository when the model grows larger?  

Depends on what you define as large