|
|
Key Benefits of Database Change Management with TeamWork
- Adopting TeamWork results in higher quality projects from development teams, safer synchronizations, and no code loss. This reduces risks when deploying changes to production. The end result is increased production uptime and improved customer experience.
- TeamWork maintains a complete repository of database changes, provides a full audit trail, protects development assets, increases productivity, and provides the ability to roll back changes if a crisis occurs.
- The content management functionality of TeamWork for your metadata content changes results in all project assets being versioned so change management is truly complete providing the ability to recreate environments for debug, crisis recovery, investigation of changes, etc.
- Requirements-based deployment allows changes to be deployed based on true organizational requirements and not on technical constraints - deploy what you need and not just what you have.
|
|
Today - without dbMaestro |
Potential Damage |
Risk Avoidance With dbMaestro |
|
Database updates performed by multiple users creating conflicts and data loss |
Productivity loss and quality issues |
Policy is enforced, updates are allowed only by disciplined SCM process |
|
Changes are applied without proper workflow |
Degradation of process control, productivity and quality |
Standard check-in and check-out capabilities similar to other development disciplines |
|
Development/QA/Integration databases are manually created and updated |
Lost productivity, low quality, code synchronization issues |
Automated updates between multiple database environments at the change request level |
|
Documentation of database changes is done voluntarily (manually) |
Difficult to audit or meet compliance guidelines |
Provides complete audit trail of all changes |
|
Roll backs are done through manual restore |
Time to recover, difficult to figure out proper restore point, restore information is not always available |
Roll back of changes is automated for both Development and Production systems |
|
Lookup tables data is not managed |
quality, manual intervention, lack of documentation |
Lookup tables data is managed as any other object |