Share your experience using Canonical Bazaar

We are currently not using Liquibase, but we have used it earlier for database deployments. I have provided product information on the PeerSpot site.

Liquibase's valuable features include database deployment and rollback scripts, where we kept our scripts in SQL format. When we deployed using CI/CD, it connected to Liquibase and deployed those scripts to the desired database. We integrated it with CI/CD Jenkins to execute all Liquibase operations, and the logs were retained for around two to three months.

Liquibase's adaptive change scripts benefited our database management process significantly. Previously, if someone logged into the database, they could make changes without any information or change orders. We restricted the DB servers to the DB team specifically. Whenever they wanted to execute changes, they had to go through the change order process, and we would not provide them the password until then. We maintained complete logs so that if any database change occurred and an application stopped working, we had change orders to reference and determine whether it was a legitimate change or a normal variation.

Liquibase's rollback functionality impacted our deployment downtime positively. We would take a backup before anything was executed on the database while we had the change order. Once execution occurred, we performed sanity checks by the application team. If the checks passed, we proceeded. If not, we restored the same copy to avoid database outages.

Liquibase is a very powerful tool in terms of database automation.

I have not found many disadvantages with Liquibase. However, it does not have inbuilt rollback management. You have to take your own backup and restore it if there is any failure. It does not have a feature for rolling back or creating a snapshot of the existing database, so those things must be managed manually.

Liquibase could implement rollback compatibility in the future. Additionally, there were checksum errors, and the logs were not reporting properly in Liquibase, so those issues could be fixed.

I used Liquibase for around two and a half years.

They were helpful. We reached out via email or to their community support, and we received immediate responses.

I can rate their job an 8.5 out of 10.

I changed companies, which is why I stopped using Liquibase. The previous organization was still using Liquibase, and there was no switching of the product. However, I moved to a different organization.

I rate Liquibase a nine out of ten. We used the Community Edition for Liquibase.

We used Liquibase's changelog feature extensively. The changelog contains complete information about all the scripts we executed and presents it as event data.

Liquibase's CLI was powerful. We executed scripts through the CLI, and from CI/CD, we called those commands using the CLI.

We built a separate tool for monitoring the databases where we logged the query speed in terms of Liquibase's tracing and monitoring capabilities helping with compliance for our enterprise. We were not using any inbuilt tool from Liquibase. In terms of compliance and audit, we had the challenge that the compliance team would spend weeks gathering manual evidence for audits. We maintained change orders where we kept the change queries that we were going to execute on the production database from the DBA so that everything would be compliant because of these change orders.

My overall review rating for Liquibase is a nine out of ten.

My main use case for Liquibase is database versioning and change set management.

A specific example of how I use Liquibase for database versioning and change set management is that it ensures my schemas are versioned instead of losing track of them over time. Liquibase automatically rolls back changes if there are problems during a release, making the process simple.

In addition to my main use case, Liquibase has helped us solve the issue of reverting changes.

The best features Liquibase offers are the schema change sets and the change tracking on any kind of change in the database.

I definitely find that the change tracking feature makes my workflow easier.

Liquibase has positively impacted my organization by eliminating the risk around database changes.

Eliminating that risk has affected my team and business overall by removing costly downtime when trying to revert a problem deploy with a database.

I cannot think of anything at the moment regarding how Liquibase can be improved.

I am uncertain about Liquibase's AI capabilities regarding its governance and security.

I am uncertain about Liquibase's AI capabilities regarding its accuracy and reliability of output.

I have been using Liquibase for 12 years.

Liquibase is stable.

I did not previously use a different solution.

My experience with pricing, setup cost, and licensing is that it is easy since it is open source.

Before choosing Liquibase, I did not evaluate other options.

The advice I would give to others looking into using Liquibase is to make sure you read the documentation. I would rate this product 9 out of 10.