dbMaestro TeamWork’s change policy enforcement is a unique technology designed to make sure that your database's changes are following due change process and are always logged and saved. Change policy enforcement is integrated with the database engine to make sure it is never bypassed. This unique technology makes sure there are no "out of process changes". If change policy was not enforced in the database engine, but rather through an application, one could easily bypass it by using another Oracle client tool, various IDEs or even with command line tools. dbMaestro TeamWork makes sure out of process changes are denied execution, and prevented before creating any damage to the database, or your company's due processes.
To execute a command that changes a database object, the DBA or database developer must use the Check-Out Action to unlock the object within dbMaestro TeamWork. This action guarantees that each change is documented correctly. After the DBA or database developer completes the changes and performs the Check-In Action, dbMaestro TeamWork closes the change cycle by saving the object’s new definition in the repository and setting the object’s status to “locked.”
Code overrides that can happen when two developers are trying to update the same object are easily prevented using the Check-Out & Check-In actions.
Same enforcement protocol is used to deal with application meta-data that exists in configuration tables or any other relevant content that requires revision control or change tracking.
By controlling the change cycle, dbMaestro TeamWork produces an accurate audit trail of changes to the database, correlating each change (What) with the person who made it (Who), the date and time of the change (When) and the business requirement for the change (Why). dbMaestro TeamWork enables users to review the history of a single object or the entire schema and provides the capability to drill down to the change itself.