version control set-up help

[Thomask]

I seem to be going around in circles and getting confused (which some say for me is not difficult!). I appreciate that this is covered in the help files, but I just can't seem to see how to set up version control with our EA set-up.

We plan to use EA on our next project. We have the Corporate version of EA installed (at the moment) on 2 PCs. We also have a SQL server database set-up to which we can connect to over the network. We haven't started modelling anything yet, so the database on the server just holds the intial 'blank' set-up for a new project (I created a new project selecting all models, then data transfered it all  to the database on the server). We also want to use version control in the form of Subversion which we already have set-up on a different server. EA work to be carried out during the project may require 2 people accessing the models at the same time (I appreciate the implications of this). I believe from reading the help files that the configuration which best suits this way of working is the 'Single Shared Model', which is fine, but it never gets mentioned again during any of the version control help and the help implies that you need to store your work locally. I am pretty sure it is going to my lack of understanding here, but I put my hands up.  Is there anybody who can shed some light as to how we need to configure Subversion and EA?

Any help would be appreciated.

[juliancooling]

As far as I know, version control wants you to have a local copy which is synchronised with a shared repository. If you already use a shared repository (SQL server) as your working copy, the setup is not going to make sense since all changes are transparently shared.

So you will want to use a local copy of the repository using the Jet database and subversion to manage the sharing.

Others who have tried different arrangements may offer additional opinions.

Julian

[Thomask]

Thanks for the reply Julian.

I was wondering if that was going to be the case. As it is only going to be a small team, it might be best for us just to leave Subversion out of the equation.

Thanks,

Thomas