• Added an internal security mechanism – Access Roles, which enables the administrator to set permissions on object types and action to a specific user within a specific project.
• Viewing the Database Schema from a Module Point of View provides database administrators (DBAs) with a view of the database schema from the point of view of a module. This significantly increases efficiency, making the jobs of both the DBA and database developers much easier.
• The managed schema’s password can now be saved in TeamWork client, eliminating the need to enter it repeatedly.
• Adding Search functionality in Source Control window, which allows you to find objects in specific status, for example: pending changes, objects being checked-out by different user and so on.
• New platforms added:
  • Windows 2003 (64 bit) , 2008 (32 and 64 bit)
  • Windows 7 (32 and 64 bit)

Additional fixes in the new version include:

• Several issues in content management.
• Supporting truncate command.

• Known Issue: Add-In will not start when using ODAC 10g on 64bit. Click to see the solution.

The dbMaestro TeamWork™ Management Studio acts as a sort of administration console, allowing DBAs, project managers, and change managers to determine what will be managed and how. It also allows them to perform various change management tasks, such as assigning changes to change sets or analyzing alterations to schema structures or table content. Additionally, the Management Studio provides them with the ability to generate reports to audit and track any changes or modifications made to database schemas and objects. 

The TeamWork Sidebar and Plugins are typically used by application database administrators (ADBAs) and developers to conduct day-to-day change management tasks, such as making specific modifications to a database, analyzing changes, or rolling back to prior versions of the database. 

The TeamWork Deployment Manager is leveraged by project managers, change managers, and DBAs (although it can be run by any authorized user) to define what will be deployed, based on the objects outlined in the software change management (SCM) environment or an internal activity list. The Deployment Manager can also be utilized to create an autonomous package for deployment. 

The Deployment Manager also includes an innovative three-way compare and merge tool that allows users to verify their work prior to deployment, to ensure that there are no conflicts or problems that will hinder the performance of production environments. When issues are detected, it will dynamically suggest a potential resolution. 

Visit our Web site to learn more about the features and benefits of dbMaestro TeamWork, our unique change management software.

In many cases, the content of a parameter, lookup, or metadata table will have a profound impact on the behavior and performance of the application being developed. When altering any of those objects as part of a version update, developers must treat those modifications in the same way they would any other changes to code or database structure. 

Yet, many developers keep a complete set of updates for other objects, but fail to do the same for the relevant data changes. This often leads to bugs and other malfunctions that can result in downtime. 

dbMaestro TeamWork™, our innovative change management software, helps developers overcome this challenge by allowing them to define which tables are crucial to application behavior.  TeamWork’s comprehensive content management capabilities will then be automatically applied only to those specified tables. 

From then on, developers will be required to “check-out” and “check-in” table content, in order to change the values of the data within that table (i.e. insert, update, delete, etc.). As a result, they can leverage truly complete Oracle change management, with the ability to recreate tables when needed for debug, crisis recovery, investigation of changes, and more. 

Visit our Web site to learn more TeamWork’s content management functionality, as well the other features of this unique database management software.

Solutions for database version control were created for this very reason.  In addition to improving developer productivity and accelerating the release of revisions and updates, database change management solutions also help development teams to better manage and mitigate risks by automating key activities, and empowering project managers with unhindered visibility into all modifications. So, they can detect which areas of the product are not stable, monitor how frequently changes are being made over time, and determine who is making the majority of those alterations. 

A next-generation database version control, dbMaestro TeamWork™, takes the same type of insight provided by software change management solutions, and applies them to the database world. TeamWork dramatically improves risk management by:

1. Facilitating the creation and enforcement of formal, standardized change policies

2. Providing end-to-end tracking, with proactive dynamic alerts, of all schema and object changes

3. Enabling automatic rollback to other versions when errors are made

4. Documenting and auditing all modifications and related information – who made them, when they were performed, why they were made, etc. 

5. Allowing developers to analyze the impact of database version changes, before they are deployed

With our next-generation database change management solution, dbMaestro TeamWork™, companies can significantly reduce the risks associated with their database development efforts.

Visit our Website for more information about the powerful risk management features of TeamWork, or to learn more about the benefits of this innovative solution.

In order to ensure success, creating one project that includes all relevant schemas is the best approach to take. Next-generation database change management solutions, like dbMaestro TeamWork™, provide a variety of features that make it simple and easy to effectively manage projects with multiple schemas. 

For example, TeamWork provides an intuitive sidebar, conveniently located on the right side of the console/screen. Through this sidebar, developers can create a module, then assign multiple objects from different schemas to it.  These modules then serve as a sort of display filter for objects, showing users only those associated with the project at hand. This saves time and increases productivity by making it easier for them to locate only those objects to be worked on, instead of manually browsing through all objects to find what they need. 

TeamWork also offers advanced permission capabilities that empower database administrators (DBAs) with greater control over their environments. Unauthorized, accidental, or incorrect changes to schemas and related objects can be proactively avoided through granular access permissions, with each member of an IT or development team being assigned rights for only certain portions of each schema, based on their role and responsibilities in the application. 

Want to find out about TeamWork, and its unique ability to apply proven software change management (SCM) principles to the database world?  Visit our Web site to learn more.

Who will realize the most significant advantages with TeamWork, in addition to its clear and proven applicability to large, conventional database deployments?

1. Companies that employ development teams for the purpose of creating solutions to be leveraged internally, such as intranet sites and software applications for use by staff members or business partners.
2. Vendors who design and develop software applications for sale to customers, including those who create both on-premise and software-as-a-service (SaaS) based solutions.
3. Companies that perform software customizations, such as value-added resellers (VARs), consultants, or third-party solution implementation service providers.

With the help of TeamWork, organizations like these can:

• Improve project quality and the end user experience by protecting against code loss, and reducing risks when deploying changes to production – which, in turn, increases production uptime.
• Enhance compliance by creating a complete repository of database changes, which provides a full audit trail, with complete details such as who initiated the change, when it occurred, why it was made, etc.
• Better manage content, so environments can be quickly and easily recreated as needed for the purposes of debugging or crisis recovery.
• Boost effectiveness, with requirements-based deployment that allows changes to be made based on actual business needs, not on technical constraints.

Want to learn more about TeamWork, and how it can benefit your company? Visit our Web site to learn more about the features and functionality of this next-generation database change management solution.

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.

However, when it comes to databases, no such capabilities existed – until now. Traditional compare and sync tools were able to provide insight into changes from a technical point of view, but could not relate the changes to any specific activity. As a result, database administrators (DBAs) were forced to make those connections manually – identifying the alteration, then correlating it to the activity being performed or released.   

Unlike these first-generation compare and sync tools, next-generation database change management solution, dbMaestro Teamwork™, is providing a more structured and productive way to apply changes to database schemas. With TeamWork, DBAs now have the ability to deploy change-sets for both database schemas, as well as data elements. 

Changes can be instantly associated with change-sets via the TeamWork Management Studio.  When checking out, users will see an “Assign to Change-set” area at the bottom of the screen. They can then choose the appropriate task to link to from the drop down menu. This will allow users to produce only those changes made for specific change-sets. 

Read more about the ability to upgrade schemas based on activity, and the many other powerful and innovative features of TeamWork on our Web site.

TeamWork allows relevant objects to be filtered, so they are easier to locate and retrieve.  For example, developers can view only the code associated with a certain project, instead of having to browse through the code for the entire database to find what it is they need. This not only makes those developers currently involved in the project more productive, it enables new developers to join the effort seamlessly and get up to speed quickly on which database elements are being worked on. 

The ability to view a portion of database schema from a module point of view also simplifies the transition when there is a switch from one DBA to another during the course of a project.  The new DBA will be able to quickly and easily find all relevant objects, instead of having to review the entire database and figure everything out on his own. 

Visit our Website to learn more about the ability to view database schemas from the point of view of a module, as well as the other innovative features of dbMaestro TeamWork.

But, while auditors and regulators have been diligent in keeping track of alterations made in the common code used in software applications, they have not been doing the same on the database development side. Basic change details are tracked, but the origin of the change, and the reason for it, are not captured. This can create significant compliance gaps, and put companies at risk of potential fines and penalties if an audit is conducted by an external or third-party. 

While SCM can help facilitate compliance in a variety of ways on the software side, advanced database change management solutions can do the same for databases. For example, they can proactively prevent unauthorized adjustments to the databases that store the accounting information used to generate financial reports (a key SOX requirement). And, they can help organizations implement formal policies when it comes to database modification and management.  Additionally – and perhaps, most importantly – they can enable the creation of a complete audit trail of all changes made to databases, such as those that house sensitive patient data (a core HIPAA mandate). 

In other words, full compliance with all regulatory guidelines can only be achieved through the use of an innovative, next-generation database change management solution, dbMaestro TeamWork™, which applies key SCM concepts and processes to the database world.