A tool worth trying - To improve your CD

Liquibase is used by our client (in the financial domain) as part of their technology refreshment to minimize the manual effort of deploying database changes. We have integrated Liquibase with our current deployment tool uDeploy to create a continuous delivery model for deploying database changes till Production. With Liquibase in place, a couple of benefits that we have seen: To be in CD delivery, app teams are now maintaining the DB changes in version control. Make sure that came changesets are being deployed & tested across all environments till Prod. It has reduced the manual DBA effort & risk of fat-finger errors as being part of the automation of changesets deploy. Easier to adopt across all teams using different DB tools (SQL, Oracle, etc) DB changesets are now part of the quality process (running different scans as part of CI) Easier to push any changes to the Database. It is easier to roll back ANY changes (though the team needs to have rollback scripts in place with each changeset that they are deploying to achieve it). The only thing that we have observed is a compatibility issue, where we upgraded Liquibase from 4.2 to 4.9. The same changeset which we were able to run on successfully using 4.2, part of it was now failing when tried to deploy using 4.9. It's a good tool to start implementing & tracking your database changes through Liquibase and teams should explore it from their end to ensure it fits all their requirements.

We are not part of the administration of DB, but deploying changes to DB. Being part of the DevOps team, with Liquibase in place core of our CD pipeline for deploying DB changes has helped us a lot. Also reduced the dependency on the DBA team to perform every single small change.