Questions: Using EA in team environment

[andrey]

Hello all,
I have recently started using EA and overall very impressed with the tool.  I do however find team development features somewhat confusing.

1. Using Version Control allows me to check in/out seperate packages, but not the main project itself - am I missing something here?

2. Using SQL Server as data storage for the project allows me to keep the entire project easily accessible from any pc and adding Version Control on top of that allows me to check in/out parts of the project.  The confusing part is where the data is stored for controlled packages when using SQL Server and Source Safe - SQL Server, Source Safe, or both ? (I am leaning to the "both" answer which is not making much sense).

I would appreciate any help on this one (as I am responsible for evaluating tool and deciding to purchase it).

Thanks

Andrey

[ola_strandberg]

We recently evaluated EA and I must say we were very impressed and still are.

However, despite purchasing the corporate version, what we have ended up doing is to just version control a master and work on replicas.
Periodically (at the end of each day) authors check out the master, synchronize it with their replica, and check the master back in.

This is far from ideal, and there may be other implications from it but it was the best thing we could come up with.

A way to replicate between a database and an EAP file would be a start to a more robust environment I guess.

What do the rest of you do?

Cheers
Ola

[Sean Kearon]

You can right-click over a package in the project view and export/import it as xml.  (Any packages under the root are overwritten when importing.)  This give you the option of controlling the exported xml files and merging them into a model whenever you like.  There are some previous posts in here about this approach.

HTH

Sean