Use cases

You can use change management for various ends. One example is creating a gold baseline of a database as soon as it goes into production. Every week after that, you set up a scheduled schema comparison job, which compares the current state of the database with the Gold baseline.

Any changes to the production database, for example a developer adding an index, will appear in the weekly comparison report generated. If the changes are unauthorized, you will be able to synchronize production back to the Gold baseline—the unauthorized index will be dropped.

In schema comparisons, the scope can include schemas, schema objects (such as tables, indexes, and so on), or non-schema objects (such as users, profiles, or privileges). The latter can be quite useful when comparing the privileges of users between test and production—at times an application may not work in production simply because the schema had higher privileges in test, but lower privileges in production.

Another use of the change...