Model, visualize, and assure a release success
The visual database pipeline builder allows you to package, verify, deploy, and promote the database delivery pipeline. The PreCheck functionality pre-runs the next release on a provisional environment to catch errors. With extensive intelligence of the database at all times, configuration drifts, conflicts, and challenges that can hinder a successful deployment to your database are identified, flagged and managed.
After completing a deployment, DBmaestro revalidates the database’s final state to make sure the release process ended successfully while auditing all changes made.
Zero friction – from development to release
The Release Automation Module supports seamless integration with all sources of database changes, whether you’re using the DBmaestro Version Control Module, other code repositories or inserting code directly from a developer.
The release process works with standard SQL coding, which means it does not require any intermediate language like XML or an associated translator. This design provides true repeatability: Scripts introduced and tested in the integration environment are the actual scripts pushed forward as tested to higher environments.
Recognize (and prevent) configuration drift in advance
Hotfixes and versioning misalignment are an unfortunate reality many development teams face. Once the emergency is managed, a new vulnerability arises — configuration drift. The Release Automation Module identifies instances of configuration drift that would botch a successful release, prevents it, and alerts you to the precise inconsistency between environments.
Enforce company policies and standards
Set and enforce policies to align all teams and database activities. Determine what database activities are forbidden, what timing is acceptable for deployments to production, code naming conventions, and more.
Easily verify that all packages meet your organization or team’s policy standards, while preventing rogue code from running. Prevent out-of-process changes to the release pipeline by determining whether or not a direct database update is allowed.