{"id":5818,"date":"2021-08-30T11:51:18","date_gmt":"2021-08-30T09:51:18","guid":{"rendered":"https:\/\/www.almtoolbox.com\/blog\/?p=5818"},"modified":"2021-09-01T19:31:10","modified_gmt":"2021-09-01T17:31:10","slug":"database-dry-run-dbmaestro","status":"publish","type":"post","link":"https:\/\/www.almtoolbox.com\/blog\/database-dry-run-dbmaestro\/","title":{"rendered":"Database Dry Run with DBmaestro"},"content":{"rendered":"

In this article we explain what is a database dry run<\/em> and how DBmaestro<\/em> can help you get the most out of it.<\/p>\n

\"dry<\/p>\n

 <\/p>\n

What is “Dry Run”<\/b><\/h3>\n

Every DBA knows the concerns when it is time to deploy to production. Will it work? Will it break something?
\nNobody wants to fix bugs while the production environment is down.\u00a0 DBmaestro removes stress and uncertainty. With DBmaestro you can pre-run your SQL scripts against a production-like environment. It does this as part of the CI\/CD. If there is an issue in the SQL statements<\/span>, the program sends an alert.<\/span><\/p>\n

What is the purpose of a Dry Run?<\/b><\/h3>\n

A dry run (or a practice run<\/em>) is a testing process where potential failure effects are intentionally mitigated. Testing if a passenger will survive a crash for the car industry (a crash test) is an example of a dry run. So is the testing of a pilot ejection seat while the jet is parked on the ground and not in the air (from Wikipedia<\/i>).<\/span><\/p>\n

What is Dry Run in SQL?<\/b><\/h3>\n

Running the SQL scripts which are intended to run on production in a similar database environment.
\nFor instance: test your UPDATE and DELETE queries before you run them.<\/span><\/p>\n

How does DBmaestro enable you to use dry runs?<\/b><\/h3>\n

DryRun is an optional environment in DBmaestro (you may configure it when you set your Release Source<\/em> environment).<\/span><\/p>\n

The DryRun environment layer is available for projects in which the “DryRun” option has been activated. During a Package Precheck process, this environment will be overwritten with the Release Source schemas\/databases. Then the scripts will be executed to verify that they will run on the real Release Source environment.<\/span><\/p>\n

\"dbmaestro<\/a>

Illustration: Dry Run using DBmaestro (click to enlarge).
You can also integrate DBmaestro with common CI\/CD tools such as Jenkins and GitLab CI to apply the best practices of dry runs (e.g. apply developer CI feedback loop)<\/p><\/div>\n

\u00a0<\/span><\/p>\n

Mitigate risks and increase compliance and peace of mind while you deploy to production by using DBmaestro Release Automation and Dry run.<\/span><\/p>\n

Dry runs are available in DBmaestro Enterprise edition only.<\/span><\/p>\n

\nWe (ALM-Toolbox) officially represent DBmaestro and provide consulting, subscription licenses, support, training and more.
\nTo learn more about our DBmaestro offering please contact us: dbmaestro@almtoolbox.com<\/a> or call us: 866-503-1471 (USA \/ Canada) or\u00a0+31 85 064 4633 (International)\n<\/div>\n

Written by Nehemia Litterat, senior consultant at ALM-Toolbox.
\nNehemia has more than 25 years of experience in software development, DevOps, team management of both server side and front end development.
\nNehemia is experienced in Java development and improving software development processes – mainly with automation and tools supporting dev tools.
\n<\/span><\/p>\n

 <\/p>\n

<\/h3>\n

Related Links:<\/h3>\n