While managing applications’ code components under version control is widely practiced, development managers seem to ignore the exposure introduced by having database components managed outside the SCM methodology.
With the introduction of dbMaestro TeamWork for Oracle™, development managers are now able to cover the database components of their applications with the same disciplines covering the code and all other components, such as collaboration enablement, audit trail of changes (check-out, check-in), versioning, and the ability to undo or rollback changes.
The most important principle in the SCM methodology is that all application components, whether code or database, must be under version control and documented. Therefore, when database changes are not covered – the version control solution is not complete.
TeamWork for Oracle™ is the only database version control software that enforces a change policy for database objects in the database level. Additionally, TeamWork carries the benefits of version control to downstream environments by helping enhance the quality of deployment scripts and reducing the time required for their preparation.