DbVisualizer is a multi-database tool for developers, analysts and database administrators, providing a single interface across a wide variety of operating systems. Boasting an easy-to-use and clean interface, DbVisualizer runs on all major operating systems and supports all major RDBMS that are available. Users only need to learn and master one application. DbVisualizer integrates transparently with the operating system being used.
$0
Liquibase
Score 8.0 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…
N/A
Pricing
DbVisualizer
Liquibase
Editions & Modules
DbVisualizer Free
$0
DbVisualizer Pro with Basic support - Renewal
$89
per year per user
DbVisualizer Pro with Premium support - Renewal
$119
per year per user
DbVisualizer Pro with Basic support
$199
per year per user
DbVisualizer Pro with Premium support
$229
per year per user
No answers on this topic
Offerings
Pricing Offerings
DbVisualizer
Liquibase
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
New license cost includes a perpetual license, software upgrades and support for the length of the term. 1, 2 & 3 year terms are offered. Once license expires the user may access all Pro versions released before the license expiry indefinitely. To gain access to Pro versions released after the license expired, license renewal is offered. Volume discounts apply to both new and renewal licenses.
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 …
Well suited for medium size to large Oracle system that includes a large and complex database schema with many database objects including functions and triggers. Also well suited for a medium size to large Microsoft SQL Server system with many complex database objects. Its SQL editor and query builder are well suited in developing complex SQL queries.
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.
does not handle lost connections well (specially after stopping a running query) (mysql). eg. after hitting stop, and then hitting run again, it can sometimes look like its running the query, but it isn't actually!
filtering on databases window is clunky (why the need for filtering certain object types at a time? just filter everything, google style)
altering table, adding columns (NOT to the end of the table's columns, but earlier) is not supported (mysql) even though the db supports it (alter table add column BEFORE..)
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.
I use this tool for several hours each day, spanning many years in various projects. It's wide support for various database types while keeping consistency within the UI for each is important when working with various databases day in and day out.
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.
[DbVisualizer] is pretty easy to use compared to IntelliJ because of it's simplicity. The performance is very good, it feels as good as a native application compared to the other two softwares I used for the same purpose. It's very cheaper compared to the other two tools and that's a big selling 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.
The only point I could potentially give is hours saved by having so many warehouses hooked up in one place vs. having to manage connection string changes/password updates across multiple applications... maybe 10% decrease in time spent managing connections? Mind you, I've had everything hooked up on DbVis for close to 6 years so it's hard to remember the "before times"
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.
