DataGrip, from JetBrains, is a database IDE that is tailored to suit the specific needs of professional SQL developers.
$99
per year per user
Liquibase
Score 8.7 out of 10
Enterprise companies (1,001+ employees)
Liquibase is a database change management tool that extends DevOps best practices to the database, helping teams release software faster and safer by bringing the database change process into existing CI/CD automation. According to the 2021 Accelerate State of DevOps Report, elite performers are 3.4 times more likely to incorporate database change management into their process than low performers. Liquibase value proposition: Liquibase speeds up the development…
I think it blows away mysql workbench hands down. Workbench does have more functionality when it comes managing the mysql instance, viewing performance etc. Navicat is ok, it might be better for new database develoopers. I stumbled upon DataGrip cause it came with jetbrains …
DataGrip provides a single UI for many DBMS platforms, instead of using one for each. Because of that, you can migrate things between platforms using the tool and "look across" all databases at once.
DataGrip is the most widely used software for simplified data management; we can know what is missing and what is leftover. The interface is straightforward and with a lot of security in its use of the system. All this has been its plus point.
DataGrip makes it easy to access and manage multiple databases locally and remotely, simplifies everything, and has powerful integrated features and resources that allow you to visualize and analyze data from a single platform.
In my previous project and organization I have used Flyway for database change management and version control similar to Liquibase which I am currently using. Comparing it with Flyway, Liquibase provides more feature flexibility and enhancements to handle complex workflows with …
None of the products we looked at really focused and had good tools for Database Version control at the level we needed. Our monolith system just does not work well with them. We want to change it from a monolith, but we have to version control it first before really making …
The functionalities in general were very similar, but Liquibase was less intrusive and had a larger community, which made incident resolution more agile without depending on the support of the platform itself.
Liquibase met our needs in a better way, even with the free version alone, then we decided to upgrade our license in order to be able to access policy checks baseline feature
With Flyway you need to Write rollback scripts manually. With Liquibase we have a lot of customization with to rollback with options such rollback-one-changeset or rollback-one-update.
There are many things done differently and in a smoother way when it comes to Liquibase. The CI/CD setup flow is easier. Switching between the different versions on different environments is really easy. The UI of login portal is user friendly and easy to use. Overall, it has a …
Liquibase supports a wide range of database management systems (DBMS) including MySQL, PostgreSQL, Oracle, SQL Server, and more. It is written in Java and offers command-line, XML, YAML, and JSON configurations. where as Alembic is primarily targeted at SQLAlchemy users, which …
There is no real competitor when it comes to what Liquibase does - at least not at the time we considered it three years ago. It was an easy choice in this regard, but we could have said no to it if it made our workload more difficult. But our proof of concept showed there were …
We adopted Liquibase to complete our Ci/Cd scenarios. Without Liquibase, DB changes were out to scope in our DevOps scenarios. Log and accountability are more clear now.
Liquibase makes it easy to integrate into CI/CD pipelines, keeping the database and code in sync. The switch from one database management system to another is made easier by modeling the structure of the database in DBMS-independent XML rather than SQL. A user-friendly web …
Liquibase is much more powerful compared to Flyway since it is much more flexible in nature. You can apply changes programmatically, works with any kind of database and provides features version controlling database schemas. All these features were missing in Flyway and that's …
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.
It is undoubtedly one of the best database management programs. It dramatically simplifies database management and administration. Its extensive support for various database engines is a point to highlight when we talk about DataGrip; you will like having such a powerful resource much as we do.
Any Codebase that does schema or table changes all the time for development or where Development and code is mostly in the database or SQL liquibase is a must. In a codebase where the database is pretty static or is just a place to dump data, liquibase is probably too much. You also need to have a team for it to really make sense. Doing a solo or small team project doing full version control on the database is probably more overhead than it is worth.
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.
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.
Perfect other than a way to handle saving and re-using queries. A simple/better way of creating a pool of queries for each project or database connection would be very helpful. It is not bad now, just could be a better. I have used Navicat for MySQL in the past it had that feature. It could save all your queries to the cloud and you could use them on any device.
Liquibase has several features, on their free plan, that matches exactly our expectations and needs: this already makes it standout from its competitors. On top of that, the setup was straightforward: we are running an integration with Databricks, and there were only two steps truly needed, install the driver and the plugin, done. This is the type of seamless experience our team appreciates the most when evaluating a tool or service.
Liquibase's customer support team has been very instrumental in helping us drive the whole Database CI/CD initiative. We have always received very quick resolution to our queries or any roadblock we hit. Right from setting up Liquibase in our environment to this date the Liquibase team has always helped us deliver quality and innovative solutions.
DataGrip is the most widely used software for simplified data management; we can know what is missing and what is leftover. The interface is straightforward and with a lot of security in its use of the system. All this has been its plus point.
In my previous project and organization I have used Flyway for database change management and version control similar to Liquibase which I am currently using. Comparing it with Flyway, Liquibase provides more feature flexibility and enhancements to handle complex workflows with rollback capability and its usage of contexts and labels allow us to target changes to specific environments, which Flyway doesn’t support natively. Also Liquibase provides way to compare different schema and generate changelogs for syncing environments automatically where in it allows to have declarative schema management by using XML/YAML/SQL script format.
We are still in the early phases, where the costs are potentially greater than the benefit. Trying to get Liquibase integrated into a pipeline has taken time investment and required some trial and error.
We are still a relatively small shop with a relatively small number of schema changes (perhaps 1 every week or so). As such, we aren't at a place where we couldn't have managed control of this without a tool. However, there is no doubt that investing in a tool at this stage was the right move. Now we have established guidelines and a pattern for how to do schema changes in a way that will make things easily scalable as we continue to grow.