Book a Demo

Author Topic: Using SQLServer as repository with SVN  (Read 2576 times)

Mike M UK

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Using SQLServer as repository with SVN
« on: September 02, 2011, 09:18:56 pm »
Hi,

I work for a major software company and we have just ordered a handful of licenses for EA corporate edition, with a strong possibility of going site wide. I am currently investigating how the versioning works and to successfully integrate EA into our current setup.

We have models for 3 seperate projects with the possibility of more as time goes on. We have a centralised environment so anyone who works on the models will be in the same office on the same network.  We use SVN for version control and what we want to do is store the models in SQLServer and allow any developer to connect to this, lock the package/class they are working on and then unlock when done. I have this working successfully so far although it is just a test environment with 2 users. What I need to know is the following:

Where does SVN fit into all this? If the models are stored in a SQLServer database how does EA handle the versioning and baselining? Is the baseline stored in SQL Server?

How does EA handle branches when the model repository is SQL Server? So for example if we were just using SVN as a repository and we have a product release and branch at that point in time, some engineers can work on the product release branch while others can continue working on the main development branch as SVN automatically deals with this. If we are storing the models in SQL Server how would we achieve the same behaviour? Is it a case of manually branching the database schema ourselves?

I have read through the version control document provided but need some answers specific to our needs.

Thanks in advanced.

OpenIT Solutions

  • EA User
  • **
  • Posts: 555
  • Karma: +9/-1
    • View Profile
Re: Using SQLServer as repository with SVN
« Reply #1 on: September 03, 2011, 12:14:34 am »
Hi Mike,

A brief answer to your questions:

- the baseline feature built into EA will store a baseline in your database of the packages selected for the baseline.
- the source control system if configured can also be used to create baselines/branches etc but these are stored in the source control system - as xmi (xml) files.

The benefit of using version control above and beyhond the database and built in baselining is that you will have much finer control of versoning, so for example you can rollback to a change to a specific element quite easily.