DBeaver vs. MySQL Workbench

If you are connecting to Snowflake and want to query from your laptop, I find that this is much easier to use than Snowflake's IDE. It allows us as a business intelligence team to more easily connect to our servers, and code with much less hassle. It would be less appropriate if you are only on an on-premises SQL server, in that case, I would just use SSMS.

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

• Identify types of DB connections by color code: development, testing and production.
• Predictive typing, it is incredibly accurate and saves me a lot of time.
• Jump between different simultaneous DB connections.
• Navigate through the schema object tree.
• Provide all the tools I need in one window.

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

Incentivized

• Schema editing is not very intuitive. Editing a single column forces you into multiple tab windows when trying to change something simple like a column name.
• Sorting and filtering in data is nice, but buried in long right-click menus.
• Some things are definitely non-standard UI for a Windows application, so it might be hard for die-hard Windows fans to get used to.

Incentivized

• 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

It's perfectly easy to use. Not super new and shiny with lots of accessibility tailored tools, but does the job

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

Not a lot of users have DBeaver so fewer resources are available online to help you if you have any issues. When I was trying to figure out how to create my own ER diagrams, it was a little tough to find resources

Incentivized

MySQL workbench from MySQL only supports MySQL databases and it only provides basic functionality. On top of that, the user experience could be quite confusing for first-time users. SSMS from SQL server doesn't support inline editing nicely. The view for inline editing and view data is different, making it uncomfortable to use. All in all, DBeaver is the best tool when you manage a lot of databases with different types.

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 Ability to manage DBeaver and query ad-hoc quickly
• By having the queries saved it has saved developer time and thereby increased the ROI on the investment on the tool
• This has made firefighting quicker and freed up resources for more development work.

Incentivized

• 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