dbMaestro TeamWork prevents unauthorized changes to your database and produces an audit trail that tells you Who did What to your database, When they did it and Why it was done.
In many organizations, developers can change database objects including functions, procedures, packages and table content, but DBAs can change all objects including table structures. On the other hand, QA users can make changes in QA environments but not in development environments.
As a practical matter, developers and DBAs often work on the same Oracle user account – the owner of all database objects. In addition, many organizations use the same Oracle user account password in all environments: Development, Integration, QA, Pre-production, UAT (User Acceptance Tests) and, in some cases, even in Production. As a consequence, without dbMaestro TeamWork, every developer, QA user and DBA can change any database object at any time in any environment.
dbMaestro TeamWork's enhanced security mechanism controls changes to Oracle database objects at the Windows account level and group level. dbMaestro TeamWork lets you easily define a database change policy that prevents undocumented database changes, controls who can do what, and records what they did, when they did it, and why they did it.
dbMaestro TeamWork enables the administrator to grant each user different access levels in different environments. For example, developers can be given access to change functions, procedures and packages in the QA and Development environments but only be given access to review history in the Pre-production environment.
dbMaestro TeamWork’s enhanced permission management facility provides you full control over who can implement changes in a database. This lets the administrator proactively prevent unauthorized changes to database schemas and related objects. dbMaestro TeamWork can grant very granular access settings by giving users, based on their role and responsibilities, permission to change only certain parts of each schema.