Hello dear community.
Our main model database is now 5 years old, and contains about 2 500 models and 25 000 objects.
Our versioning approach and release cycle management have been a bit chaotic as we were Aris newbies and learned along the way.
As a result our database is in a "mixed' state, some parts of it are well under control and others could be ... in a better shape.
We are considering refreshing our database to start on a right foot as follows :
- We would copy our database A to a new database B . B, as A, will have many versions, some containing unapproved models.
- We would then cleanup the database B, and :
- delete outdated models ,
- move validated objects and models present in the "projects" section to the "library" section
- move "in progress" models which are wrongly in the library section to the "projects" section
- etc
- Afterwards we would create a brand new empty versionable database C and merge into C the main group of database B
- We would then have a "clean" C database, without any versions
-
We would finally create in C our first version containing the "library" section (excluding then the "projects" section) and publish database C on Connect
Have you been in such a situation ? How did you handle it ?
I would welcome your comments ?
