DBmaestro, the pioneer and leading provider of DevOps for Database solutions, today announced the release of TeamWork 4.5. The new version is the first tool to provide impact analysis to database deployment with SQL Server. In addition, TeamWork V.4.5 also has full blown support for database continuous delivery and uses baseline aware analysis, allowing more accurate determination of desired changes. DBmaestro TeamWork also supports Oracle.

Dealing with database deployments presents a host of unique challenges; unlike other software components and code or compiled code, a database is not a collection of files. It is not something one can just copy from development to testing and to production because the database is a container of a company’s most valued asset – the business data, which must be preserved. It holds all application content, customer transactions, etc. In order to promote database changes, a transition code needs to be developed – scripts to handle database schema structure (table structure), database code (procedures, functions, etc.), and content used by the application.

DBmaestro TeamWork is the only database change management solution which uses baselines in the impact analysis, thus making the nature of the change known and allowing for the correct decision, whether to promote the change, protect the target (ignore the change), or merge a conflict. DBmaestro Teamwork ensures the deployment script handles conflicts, and merges them. This reduces operational risk, provides safe deployments, and prevents unintentional code overrides.

“With this new release of TeamWork, we have introduced end-to-end continuous delivery for the database to our SQL Server customers,” said Yaniv Yehuda, co-founder and CTO of DBmaestro “We have seen time and again the necessity of controlling the database changes as soon as they are created, in development. DBmaestro applies the correct process to database change management, it ensures there are no issues during deployment by actually validating each change, in development, via impact analysis and guaranteeing that it is it is aware of the current environment status ensuring a safer, more reliable database.”