dBMaestro TeamWork™, next-generation database change management solution, includes a powerful, yet intuitive deployment manager. In this post, we’ll guide you through the use of its core features, to achieve seamless deployment – every time.
Selecting Your Source and Destination Schemas
At the top of your dbMaestro TeamWork™ Deployment Manager screen, select your source database by clicking the “Browse” button next to “Specify the source schema to integrate the changesets from”. When the pop-up window appears, highlight the appropriate schema version, and click “Select”.
The TeamWork Deployment Manager will automatically make this schema the baseline, for conducting deep analysis in later steps. To choose a different schema as your baseline, click the “Change” button. When the pop-up window appears, highlight the schema you’d like to use, and click “Select”.
For more information about what a baseline is, and why it is important, read the blog post titled “Customer Experience – Three-Way Comparison Using dbMaestro TeamWork”.
Next, you can choose your destination by clicking the “Browse” button next to “Specify the destination schema to integrate the changesets to”. When the pop-up window appears, highlight the appropriate database, and click “Select”.
When you’re finished, click the “Next” button at the bottom of your screen.
Selecting Source Type
Once you’ve selected your source and destination, the next screen that displays will allow you to select where TeamWork Deployment Manager will acquire the source schema (archive version, changesets, CM Label, etc.) from. This will enable you to deploy an archive version of the schema, a set of changesets, or specific objects as you wish.
The following screen will ask you to choose the deployment details for your destination schema, such as the database you wish to compare it to. Once you’ve made your selections, click “Next”.
Using the Merge Wizard
Our TeamWork Deployment Manager provides an innovative three-way compare and merge module. Read more about the modulein the blog post titled “Three-way analysis and merge: advantages vs. traditional compare and sync tools“. It will allow you to verify the choices made in prior steps, before executing your deployment. Review the information displayed. If it is correct, click “Finish”.
As the deployment is executing, the TeamWork Deployment Wizard will conduct comprehensive change impact analysis, notifying you of any potential issues (such as conflicts) in both schemas and data elements, and recommending a course of action for each.
First, you’ll need to compare schemas. Use the drop down menus next to each changed object to change the course of action, if needed. When you’re finished, click “Next”.
The pop-up window will show a side-by-side comparison of all conflicts in the source, baseline, and destination schemas. After reviewing, click on “Generate Merge Script” at the bottom of the screen to automatically resolve merge conflicts using the courses of action selected on the previous screen. When you’re finished, click “OK”.
Next, you’ll need to do the same for data modifications. Move to the “Data Comparisons” tab to review those data elements that contain merge conflicts, and the suggested course of action for each. Use the drop down boxes in the “Action” column to change how certain conflicts should be handled, if required. When you’re done, click “Next.
The following screen will show you which rows were updated, which rows were added, etc. Check the boxes next to the table rows you want to deploy, click “OK” at the bottom of the screen, then click the “Generate Data Deployment Script” button on the left.
Review the script when it appears in the bottom pane. If everything is correct, click “OK”.
Go back to the “Deployment Comparison Results” screen, and click “Next” at the bottom.
The final screen that appears will allow you to review the upgrade script, as well as the execution plan.
To view the video tutorial on using the dbMaestro TeamWork Deployment Manager, check out the dbMaestro “How to” video collection on our Web site, or visit our YouTube channel.
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 change management, oracle database version control, oracle version control, SCM, SDLC, Software Change Management, Software Development Life Cycle
[...] 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 [...]
[...] Teams should then deploy their changes to the integration environment using the dbMaestro TeamWork Deployment Manager, and save the deployment script. When the integration process is completed, the integration owner [...]