Database Versioning: Using Liquibase
Last week I wrote an article about Database Versioning called Database Versioning: The ignored aspect of version control. In the article I stressed the importance of versioning the changes made to databases and methods that can be used to do so. I suggested existing tools can be used to version databases and if tools were lacking then with the help of simple automation and policies database versioning can be achieved. The article received very good response including lots of comments and a lively discussion on reddit which can be found here. I also received a lot of suggestions for tools that can be used for versioning databases including Red Gate SQL Source Control, Liquibase, Delphix, FluentMigrator, Golden Gate, South, FlyWay, DBGeni and sqitch. So I thought I would try some of these out in real world scenario. As I go along I will also get to learn about these product. So let's start with Liquibase.
You can read more about how I got up and running with Liquibase in couple of hours here. Database Versioning: Using Liquibase
DevOps DataOps consultant (Data platform, AWS, Kubernetes, Azure, QA automation , CI/CD expert, "shift left")
10 年Nilesh, one more to consider: DBMaestro . https://www.dbmaestro.com/ I got a demo from them, it looks good. I've been using Redgate a lot too. It's quite powerful. At that time (2 years ago), the documentation for controlling the tools via command line was not great. But it actually works. Which helped integrating it with Jenkins or other CI tool. We have been using all along our delivery pipeline, applying changes to all environments, even production. It's worked well, although our schema was quite simple.