One of the questions we hear most frequently from our new users is, “What will the work process flow look like once I have implemented database version control solution – dbMaestro TeamWork™?” In this post, we will address that common question by outlining the process in full detail.
Initially, TeamWork will create a base version (or a label). This will serve as the baseline database, so all future database changes made can be compared and analyzed against it. Tasks will then be allocated to developers and database administrators (DBAs) or assistant database administrators (ADBAs). They will be performing such activities as making changes, creating specific revisions in the version repository, and linking those modifications to certain tasks, such as adding features or fixing bugs – much in the same way as software developers would do when working on application code – using the change management software solution.
Once a work cycle has been completed, the release manager or project manager will determine what features or groups of bugs will be promoted to the testing or integration environments (and later, to production). Next, a deployment package will be generated both from the build engine of your software change management (SCM) system, as well as from within the TeamWork Deployment Manager, based on the terminology as defined within the SCM.
Finally, a new label will be set, and a new work cycle will be initiated.
Visit our Web site to learn more about TeamWork’s features and benefits.
Tags: Change Management Software, database change management, Database Change Mangagement, database configuration management, database deployment manager, database management software, database schema control, database version control, oracle, oracle change management, oracle database version control, oracle version control, SCM, SDLC, Software Change Management, Software Development Life Cycle
