Likelihood to Recommend Store versions of DB's and Schemas this is useful for every software developer company that works with Databases. Now days al the software use a DB and control those changes are a must. have the power to rollback safe has change the way that we work. This increase speed in development while increase the business confidence.
Read full review We use SQL Compare to troubleshoot performance problems quite a bit since our data model is more like a template and not everything is 100% in sync and customization occurs between different client databases. We continually get pulled into performance issues and the developers will say Client A is performing different than Client B, why? Using SQL Compare, we usually find that one client was tuned and had indexes altered or added that weren't deployed to all clients or other objects weren't deployed correctly during the release. On the other hand, since our data model practices allow client databases to drift I tried to create a new golden image by trying to compare multiple databases based on the same data model and found it to be a very difficult process to complete using SQL Compare. SQL Compare gave me too much information and doesn't allow enough filtering to eliminate a lot of the noise.
Read full review Pros It's a useful tool for managing database versions and aiding in the development of database CI/CD pipelines. The deployment and management of database updates are simple. It provides quality checks to spot problems in DB scripts and DB pipeline views to track changes made to DB. Read full review Simple and easy comparison of database schemas and data. Differences can be copied or synced from one database to another with a click of a button. You can save "projects" so that you can easily rerun a previous comparison whenever you need to. It has a very simple, easy to learn interface. I've never needed to read any documentation or watch any tutorials in order to figure out how to do something. Read full review Cons Reducing Compatibility issues, when 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 We are not able to see detailed logs (for different changes) in uDeploy when deploying changes through Liquibase Liquibase should rollback the if any one of the changes fails. Read full review Pricing.... I wish there was an inexpensive developer version I could buy for myself. Portability.... I would like to use it from a flash drive so I can use it where ever I am asked to work. Unbundled.... This may be available already but I dont' recall I can buy it cheaply as a stand-alone product. Its only part of the bundle - cost effectively. Read full review Likelihood to Renew We are and will continue using Liquibase and it has become an integral part of our portfolio offering, any new product is by default adopting Liquibase stack.
Read full review Usability Build process is too time consuming and getting extra DB instance takes a toll
Read full review It's a good tool to have, but becomes expensive to buy a user license for each developer.
Read full review Support Rating Liquibase's customer support is at the top of my list of all vendors I've ever worked with over my 12 years of experience. They work directly with you to be successful, and response time is second to none. Liquibase is committed to getting customers up and running and - more importantly - successful in their organization and becoming champions of the product.
Read full review They have a great community website where you can search for answers but are also very responsive when it comes to direct support.
Read full review Implementation Rating the database deployments helped us with increased productivity, faster delivery and low risk.
Read full review Alternatives Considered To be honest, the option of having a free community plan to start testing in a test environment, followed by taking it in production a few months is a great way to evaluate wether or not to do the subscription based plan.
Read full review I've used Visual Studio Database Projects for this type of work in the past with some success, but Redgate SQL Compare is faster, more transparent, and simply easier to use. Faster is self explanatory. More transparent, means that it's much easier to set up your desired options for schema change deployment scripts. Easier to use, It's really dead simple. Start a project, connect your source, connect destination, click compare.
Read full review Return on Investment We need to re-educate developers to use Liquibase. In some cases, it is hard to align when several teams work on the same DB. On the other hand, Liquibase provides order and consistency in managing DB changes. Evidence and traceability are a plus. Read full review Makes deployment fairly simple. Cutting our deployment time down. With the SDK, we can customize our deployment process very quickly and easily. History is not great, it does create scripts you can go back and see but it would be nice to have a quicker version view by object to save time. Read full review ScreenShots