Liquibase for easy database administration
December 08, 2022

Liquibase for easy database administration

Anonymous | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Software Version


Overall Satisfaction with Liquibase

We used Liquibase to manage the database structure in our application. The problem it solved for us was to make it efficient to deploy a new version of the application easy and still make sure the database structure was updated so it matched the database version. We also used it to fill the database with default data.
  • Automatic upgrade of database structure
  • Supporting multiple database product
  • Bundle with application
  • Graphical user interface to manage database scripts
  • Automatic generation based on database structure
  • Less time spent to manage database structure
  • Shorter downtime during application upgrades
  • Less inconsistencies when supporting multiple database products
Everyone in the team was able to deploy a new application in their development environment even if they didn’t understand the database DDL language. We was able to easily manage multiple test environments with different version of our application in each environment. Basically it made the database administration significantly easier.
We didn’t really have to use the customer support since we were able to solve the problems ourselves with the available documentation.
Liquibase is preferred over Flyway if your engineers doesn’t have knowledge in the DDL language used in each database product supported. If you only need to support a single database product and your engineers have the skills I would recommend Flyway instead. Liquibase is preferred if you need to support multiple database products or need official support.

Do you think Liquibase delivers good value for the price?


Are you happy with Liquibase's feature set?


Did Liquibase live up to sales and marketing promises?


Did implementation of Liquibase go as expected?


Would you buy Liquibase again?


It well suited if you need to support multiple database products and want to ensure the database structure is the same independent of database used. It’s a bit less useful if the users prefer to write raw DDL script for each database product to ensure optimal performance in each case.