It's hard to move without DevOps. The information technology industry appears to have somehow latched onto the need to remind us that there is a thing called the operations team and it connects to the programming function. While we remain laser focused on Dev, we will consider the Ops and DevOps end of the global news stream from time to time.
With this caveat in mind, let us consider information detailing DBmaestro's release of TeamWork 4.5 as a DevOps for database tool that now provides "impact analysis" for database deployment with SQL Server.
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.
Unlike other software components and code (or compiled code), a database is obviously not a collection of files, explains the company.
"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, and so on. 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," explains Yaniv Yehuda, cofounder and CTO of DBmaestro.
DBmaestro TeamWork 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," said Yehuda.