Several weeks ago, Microsoft released security update which by installing it caused to dbMaestro TeamWork™, innovative database management software, to stop working.

In the security update there were two updates 982167 and 982168. After installing them dbMaestro clients were not started and the following message appears in the log:

“Message: 1) Error Source: Extreme.TWUserAgent.DatabaseAgentsContainer..ctor
Error Message: System.TypeLoadException: Could not load type ‘System.Security.
   Authentication.ExtendedProtection.ExtendedProtectionPolicy’ from assembly
   ‘System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′.
at Extreme.TWUserAgent.DatabaseAgentsContainer..ctor()
at Extreme.TWUserAgent.DatabaseAgentsContainer.get_SingleInstance()
at Extreme.dbMaestroTeamWorkGlobalUIEntities.SideBar.ControllerMainSidebar.
   ConnectController(String teamWorkControllerServer, String teamWorkControllerPort,
   String teamWorkSecurityPort, String teamWorkRmsPort, Boolean checkLicense)”

dbMaestro reported this issue to Microsoft and the temporary solution was to remove the problematic KBs from the system (982167 and 982168).

Few days ago Microsoft released a formal solution for the problem.

dbMaestro Support Team

support@dbmaestro.com

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.

Next, we’ll highlight how to conduct routine activities within our innovative database version control solution, dbMaestro TeamWork™, using the sidebar, which is conveniently located on the right side of your TeamWork console. If you cannot see it, you can open it by right-clicking on the sidebar icon in your taskbar. 

Assigning Objects to Modules

To get started, you’ll need to open the project you want to work with.  Click on the second icon from the left at the top of your sidebar.  When the pop up window appears, choose the appropriate project and click “OK”.

You can add a new module to the project by left-clicking it in the tree, and selecting “Add New Module”.  When the pop-up window appears, enter the module name and click “OK”.

Next, choose the database you wish to select objects from under “Data Connections”.  Note, you will be prompted to enter a password for each data source you select.  Once your password has been entered, click “OK”.

All objects within that database will then be displayed.  Highlight all the ones you want to assign (you can select multiple objects simultaneously), then left-click and select “Add Object to {module name}”. 

When you’re done, those objects will appear under the module in the tree. 

Checking Out

To check out objects assigned to a module, left-click the object in the tree within your sidebar, and select “Check Out Object Definition”.  When the pop-up window appears, make sure you’ve chosen the correct object, and click “OK”. 

Go to your Oracle SQL development environment to make any needed modifications to the object. 

Analyzing Changes

To review and analyze the changes you’ve made, go back to your TeamWork sidebar, left-click on the object, and select “View History”.  A pop-up window will show all changes made to that object. 

Click the “Compare to Live” button on the right side of the screen to compare the saved object definition to the live version.  Another pop-up window will appear, displaying all alterations made to both the saved and live objects.  If all changes are correct, close the windows. 

Rollback Changes

To rollback your changes, left-click on the object in the tree within your sidebar, and select “Rollback DB Object Definition”.  When the pop-up window appears, choose the revision you wish to revert back to from the drop down menu, and click “Rollback”.

You can also rollback changes by left-clicking on the object in the tree, and choosing “View History”.  Highlight the revision you wish to revert to in the pop-up window, then click the “Rollback” button on the right side of the screen. 

TeamWork will ask for confirmation of the rollback request before executing.  If everything is correct, click “OK”, then close the History window. 

Checking In

To check in the changes you’ve made, left-click the object in the tree, and select “Check In Object Definition”. 

When the pop-up window appears, make sure you’ve chosen the correct object, and link it to any related tasks in the “Assign to Changeset” drop-down menu at the bottom.  When you’re done, click “OK”. 

To view the video tutorial on using the dbMaestro TeamWork sidebar to perform day-to-day tasks, check out the dbMaestro “How to” video collection on our Web site, or visit our YouTube channel.

In this post, we’ll discuss how to perform various day-to-day tasks within our innovative database version control solution, dbMaestro TeamWork^TM Management Studio.

Checking In and Checking Out

From your database management software, dbMaestro TeamWork^TM, Management Studio console, select the database you want to work with from the tree on the left. You’ll be prompted to provide your schema password, click “OK” once you’ve entered it.

All database objects will then be displayed in the center of your console. Left-click on the appropriate object, and select “Check Out Object Definition”. Check to make sure the right object has been selected in the pop-up window, then click “OK”.

You can update the object, using the tool of your choice.

Next, go back to the database configuration management software, dbMaestro TeamWork^TM Management Studio console, left-click on the object that was changed, and select “Check In Object Definition”. When the pop-up window appears, enter in notes about the alterations made in the “Comments” pane, and click “OK”.

Associating Changes to Change Sets

When checking out, you can link changes to tasks in the “Assign to Changeset” area at the bottom of the screen. Choose the appropriate task to link to from the drop down menu, and click “OK”.

Later on, this will allow you to produce the changes made for specific change-sets, while ignoring other ones. For example, you can deploy changes to address one bug, yet skip over modifications related to other bugs that are not yet mature.

Analyze Schema Structure Changes

To review changes to schema structures, left-click on the database procedure in the center of your screen, then select “View History”. When the pop-up window appears, highlight the revisions you wish to compare, and click on the “Compare Revisions” button on the right side of the screen.

Another pop-up window will display the changes made in both the base schema and the compared schema. If all alterations are correct, close the window.

Evaluate Table Content Changes

To review changes to table content, left-click the appropriate table in the center of your console, and select “Check Out Data”. When the pop-up window appears, make sure you have chosen the correct table, and click “OK”.

Next, you can update the table’s content, using the tool of your choice.

To check in the table change, return to the dbMaestro TeamWork^TM Management Studio console, left-click the table in the center of the screen, and select “Check In Data”. When the pop-up window appears, make sure you selected the right table, then click “OK”.

Left-click the table again, and choose “View History”. When the pop up window appears, select the revisions you wish to compare, and click on “Compare Revisions” on the right side of the screen. Another window will open to display the changes in both the baseline and the compared tables. If all changes are correct, close the windows.

To view the video tutorial on using the dbMaestro TeamWork^TM Studio to perform day-to-day tasks, check out the dbMaestro “How to” video collection on our Web site, or visit our YouTube channel.

In this post, we’ll explain the various steps required to save a database version (or label), and use it in our innovative database version control solution, dbMaestro TeamWork^TM. Saving a version will allow you to create a “snapshot” that can be referred to at any time, for any purpose. For example, it can be compared to other versions, referred to as a baseline, used to generate scripts, etc. Or, you can roll back to the version whenever needed. 

Saving Database Content

The first step is to save the relevant parts of your database within your new version. Start by left-clicking on the appropriate database in the center of your console, and selecting “Save Version”.

 A pop up window will appear, where you can enter the name, description, and other version details, and link the version to your CM tool. If you wish to archive table content, be sure to check the “Select data tables to save” option at the bottom of the window. Click “OK” when you’re done.

Another pop up screen will display. Check the boxes next to those tables whose content you wish to archive. Click “OK” once you’ve made your selections.

Comparing Versions

To compare database versions to one another, left-click the database in the center of your console, and select “View History”. In the pop-up window, highlight the versions you’d like to compare, then click the “Compare Versions” button on the right side of your screen.

The next pop-up screen will allow you to compare schemas and their associated data, indicating where objects and sub objects have been previously modified.

Reviewing Specific Changes

To drill down to more detail about individual changes, click on the button with the three dots next to the object in question. A pop-up window will display the specific changes made in both the baseline and compared versions of the database.

If all changes are correct, simply close all pop-up boxes, and return to the “History” window.  Click on “Generate Script” on the right side of the screen to create your schema script.

To view the video tutorial on saving and using versions in dbMaestro TeamWork^TM, check out the dbMaestro “How to” video collection on our Web site, or visit our YouTube channel.

Getting started with dbMaestro TeamWork™, our robust and unique database management software, is fast and easy. In this post, we will guide you some of the basic procedures, and demonstrate how to use a few of the core features.

Creating a New Project

To create a new project, left-click TeamWork Projects at the top left corner of your screen, and select “Add New Project”. When the pop up box appears, enter your project’s name, and click “OK”.

Assigning Schemas

Once a project has been created, you’ll need to add your database schemas. Choose the project name from the tree on the left side of your screen, and select “Assign Schema to Project”. When the pop up window appears, add the schema connection details, click “Test”, and then click “Next”. Note that you will be required to enter your SYS credentials for the first schema you add. When the Summary box appears, click “Finish”.

At this point, dbMaestro TeamWork™ will be familiar with the schema, but will not yet be managing it. This means that any changes or modifications can still be made. At this time, dbMaestro TeamWork™ will also identify the objects in the schema (it may take a few minutes until you see the objects in the GUI). In order for dbMaestro TeamWork™ to manage the schema, you’ll need to add the objects to source control.

Adding Objects to Source Control

To add individual objects to source control, highlight the appropriate database in the tree on the left side of your screen. All objects associated with that database will then be displayed in the middle of your console. Any of these objects can be added to source control by simply left-clicking it, then selecting “Add Object to Source Control”. Include any important notes in the “Comments” window of the pop-up box that appears, then select “OK”.

To add all objects to source control simultaneously, left-click on the database, then select “Add All Objects to Source Control”. When the pop-up box appears, enter any notes in the Comments window, and then click “OK”.

Managing Schemas and Their Content

Changes to database objects must be made from your Oracle SQL development environment. However, dbMaestro TeamWork™ will automatically invoke pre-defined rules to prevent any unauthorized or unapproved modifications from being made.

For example, a table cannot be altered if it is “checked in”. Your console will display a red lock icon next to any objects that are unable to be modified. Left-click the object you want to change, and select “Check Out Items”. When the pop-up window appears, highlight the object and click “OK”.

If you try to make the change again, you will see that it can now be successfully completed.

Enforcing Change Management

To invoke change management rules, left click the relevant table, and select “Enable Table Content Management”. When the Confirmation box appears, click “OK”. Another window will then display, where you can select the appropriate objects to be checked in. When you are finished, click “OK”.

Note that in order to invoke Table Content Management, the table must have a primary key or unique index(es).

Next, go to your Oracle SQL development environment, and choose the appropriate object from the tree on the left. From here, you can define data rules, set constraints and dependencies, etc.

For example, selecting a specific data element, such as Postal Code within the Location table, then clicking on the red X at the top of the screen, will lock it so it cannot be altered.

Once you’ve implemented your change management guidelines, go back to the database version control software, dbMaestro TeamWork™, console, left-click on the table the rules were applied to, and select “Check-Out-Data”. When the pop up window appears, click “OK”.

Finally, return to the Oracle SQL developer environment, and select the database icon with the green check at the top of your screen to deploy these rules and put them into effect.

To view the video tutorial on getting started with dbMaestro TeamWork^TM, check out the dbMaestro “How to” video collection on our Web site, or visit our YouTube channel.