Migration of SQL repository to local .eap w/TFS

[LarryFla]

We are having issues after migration. We have moved a large 2 year old SQL repository (that had no version control) to a new deployment of local .eap files using Microsoft TFS for version control. We did this for:

1. Improved performance (SQL repository is too slow with many users hitting at once)

2. Version control to protect from screw ups

We did the following:
1. In EA: Connect to existing SQL repository
2. In EA: Export entire model to XMI (creates 500Mb xml)
3. In Visual Studio: Map empty TFS repository to local file system
5. In EA: Import the 500mb XMI file into new empty .eap file
6. In EA: Create a single version control configuration pointer
6. In EA: Add packages to version control (dozens of 'key's added up to three levels deep) using the new configuraiton pointer.
7. In file system: Distribute the 150mb .eap file to a dozen users on the network.

When a user does a "Get All Latest", it takes about 15 minutes. This is not too bad. The problem is that more often than not, one of a few problems will occur (these also happen on check ins / check outs):

1. Error: DAO Error (no description)

2. Error: System resources exceeded (but plenty of system resources)

3. Takes a very long time (1 hour)

3. Error: invalid database format (corrupted .eap file)

4. EA crashes.

Is our model simply too complex (too many cross references between packages) for MS Access to handle? Do you have any suggestions to follow given our needs?

Thanks for any input,
Larry

[Geert Bellekens]

Larry,

It's not the setup I would recommend for a large model and a large number of users, but in theory it should work.
In this case I would talk to Sparx support. They should be able to help you out with stuff like this.

Geert