A customer has a 15+ year old database that contains almost all of their vehicle information. Unfortunately it was designed with an obsolete 4GL tool that produced an excellent 500 table schema that included no information about what the data meant. The need for constant intervention to investigate potential problems, and apply solutions meant memorizing hundreds of generic table and columns names. Developers and management both agreed that this situation was torturous to work with and highly error-prone

DBvolution automatically generated a programming representation of the database schema, and facilitated adding semantic information. The API included the ability to combine the representative classes into dynamic queries and to apply the changes required to the database. Refactoring as the project progressed added more semantics, like better names, more relationships, and subclasses of the data

Developers were able to work with the database with ease, include solutions in the standard source control mechanism, and build a generalised diagnostic tool to diagnose and fix a myriad of problems