ever growing eaxp file

[yonatan.lehman]

We use E 14.0 on top of SVP. Each user copies the eaxp file from the repository into a local folder and then works on that.
Recently we have noticed that this file grows very quickly and at some point reaches 2GB and get latest stops working.
Here is a typical scenario
1) eapx file size is 31,891,456  bytes
2) we check a branch out with about 50 elements - the file size changes to 83,652,608 bytes
3) We check the branc back in without change
4) We check out the same branch again - the file size changes to 135,012,352

We are pretty sure that the underlying model did not change between checkouts - it looks like the acrion of checking out seems to increase the eaxp file even though nothing in the model has changed.

Running compaction on the eaxp reduced it back near to where it started -  31,870,976 bytes

Can someone explain what is going on and how we can prevent the eapx file growing?

[qwerty]

eapx = Mickeysoft Access. In order to shrink it you have to run the shrinker. That's somewhere in the Manage (database) menu (depends on your version).

q.

[Sunshine]

As qwerty says Underneath the hood lies Microsoft access and it size expands with transactions. Presumably a merge does transactions and causes the size to increase even if nothing changed. IIRC MSAccess limit is 2GB thus it stops.. As you've discovered compacting the DB shrinks it. Sounds like your set up isn't ideal. Look at using other Databases such as SQL server or mysql would probably be better than checking in/out from SVP. Note also that V16 now supports SQL lite. If you can't use any of those DBs for whatever reason then try firebird aka feap files. To use another dB is quite easy. Just create a new empty target then do a transfer.

[qwerty]

Check out lets EA delete anything (which stays waste in ACCE$$) and reload from the XMI (increasing the size). (At least it did that ever since I used VC which is ages ago; but Sparx does not really change inside.)

q.

[yonatan.lehman]

Thanks All.
So from what I read up, it looks that we'll need to go for a DB or perhaps to a Pro Cloud server solution if we can't get a good bandwidth for people working from home - right ?

Any tips regarding which way to go for the smoothest ride ?

[Geert Bellekens]

Thanks All.
So from what I read up, it looks that we'll need to go for a DB or perhaps to a Pro Cloud server solution if we can't get a good bandwidth for people working from home - right ?

Any tips regarding which way to go for the smoothest ride ?

The new SQLite format is also a very good alternative. It's actually much faster than any other database format.

Geert

[qwerty]

Plus it's more like a database. Although tiny and not for large volumes, but the best alternative for programs like EA.

q.

[yonatan.lehman]

Hm. But SQLite means moving from v14 to V16 - which I'd like to do - but what is the cost/risk of that ride ?

[Sunshine]

If you are already paying for support then there is no additional licencing cost.
Just download and install. Next Next Finished.
If you have a corporate environment where they insist on creating a package in their software deployment system like SCCM then that may take a bit longer but not much.
Risk minimum - just the odd bug with new releases to deal with.