DbVisualizer vs. MySQL Workbench

DbVis is our tool of choice when we need to work with a wide variety of Db vendors and versions. It allows us to replace several proprietary tools for accessing and, in part, managing database systems. It gives our customers and us a single base to work on databases. No need for us or them to install, learn, and pay for multiple solutions. If one would, for example, use ONLY one dbms, e.g., PostgreSQL, then DBVis could be a bit of an overkill.

It is good software when we have to connect the database of the remote server but it is not as good as phpMyAdmin. When local server is concerned, phpMyAdmin is way better because it has more cleaner UI than Workbench. Workbench is preferred only because phpMyAdmin does not support the connection of remote servers.

Incentivized

• Out-of-the-box support for many different databases.
• Intuitive UI for interacting with data.
• Flexibility of SQL Commander for writing scripts.
• Great support for working with JSON data in recent updates.
• Database connections over SSH.
• Table relationship visualization is very helpful.
• The tree view is well organized in how it splits out schemas.

• Readily available too for quick and easy SQL queries
• Maintains upgrades
• Works across multiple OS platforms

Incentivized

• Small, but noticeable: it would be nice to be able to highlight just one column of a data output for copy/paste by clicking on the column header (a feature some of us are accustomed to from SQL Server Management Studio)
• Is there an ability to bulk import an excel file to a table in a connected SQL Server in DbVis? If so, I haven't figured that out yet. I still largely use Microsoft SSMS to import data to our team's personal SQL Server, but can easily query that server via DbVis)
• (I really don't have any major complaints - our company has tried to steer users toward DBeaver for YEARS, which I cannot stand. DbVis knocks the beaver out of the water)

• There are a lot of menus, some of them aren't needed or users who only need to send queries. I had to watch a videos on youtube to learn how to use workbench. It would be great to have some videos inside software (or links to videos on youtube)

Incentivized

We never had problems with it. It is able to connect to all data sources (Oracle, Informix, DB2, SQL Server) that we currently use.

Incentivized

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.

MySQL Workbench is useful for specifically remote databases. Remote databases generally does not have any UI and we have to connect the server via SSH and on CLI, we write the queries and it shows the data, which is quite tiering and more prone to make mistakes whereas MySQL Workbench provides cleaner way to connect and provides lot of tools, so that we do not have to write queries all the time.

Incentivized

Never used

Incentivized

[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.

Incentivized

It's like comparing a VW to an performance car like a Ferrari. If you need the performance, bells and whistles you'll want PhpStorm. If you just need to get from one place to another, MySQL Workbench will do just fine.

Incentivized

• Positive: Real time saver when working across multiple databases. At least 30-40 mins a day are saved
• Positive: Helpful for the 'quick DBA' tasks without switching to the native tools: approx 1-2 hours saved weekly
• Positive: Easy switch between environments / schemas / etc without hassle: saved at least an hour daily

• It provides good features and saves the time.
• When we use remote server, we can connect without using ssh etc. so saves the time and easy to understand.
• Do not have to write the queries to check the schema, so saves the time.

Incentivized