Recording changes

Recording changes

The Case

You need to keep an audit trail of changes made to the database during database development. Keeping track of changes made to the database is a tedious and time-consuming procedure, which is not that critical when you are under increasing time-pressure to deliver the final phase of the project. It is so easy to put aside this task.

Main goals to be achieved

Fulfilling project requirements without increasing the development time
Recording all changes made to the database for the duration of the project on a regular basis.

Our solution

Use Cross-Database Comparator Pro or Cross-Database Studio in order to generate SQL comparison reports between current and previous database versions:

Select schema objects and/or data, the changes in which you want to keep an audit trail.
Configure comparison strategy in order to produce comparison reports, schedule comparison sessions etc.;
Run comparison sessions manually or automatically. Archive a comparison report in order to keep a log of database changes;
If required, you can generate and keep the synchronization scripts together with comparison reports;

Advantage of our solution

Automated task ensures reducing time-consumption for developers
The project requirements are fulfilled
Elimination of the human error