DbVisualizer vs. MySQL Workbench

Whenever you have to access data sources from more than one database engine provider, you should consider using DbVisualizer for the task. Switching between multiples IDE consumes time and resources (memory), and you also need to learn menus, shortcuts, etc., for each IDE, while using DbVisualizer allows you to work consistently no matter which database engine you are connecting. You can use it to simply navigate through data structures, write SQL sentences or even create new tables and views, develop stored procedures, etc.

Incentivized

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

• Timed queries that add their result to the result grid for every execution are helpful. Creation of graphs also extremely helpful.
• Query history and auto-recover feature makes sure we don't lose our queries.
• Actions like exporting grids to Excel or other tools is a very easy task.

Incentivized

• 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 find it very user-friendly, everything is easily viewable and the fact that I can move modules around and customize the colors and appearance of things really helps make it more usable. I also find the default keyboard shortcuts intuitive and the in-program descriptions are easy to follow and understand.

Incentivized

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 provides a good value when compared against other 3rd party products with similar features as well as products with similar functionality made by the database vendors. The user interface is good and user friendly / intuitive and easy to learn. It doesn't take too long for an experienced DBA / database developer to come up to speed.

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