DBeaver offers comprehensive data management tools designed to help teams explore, process, and administrate SQL, NoSQL, and cloud data sources. DBeaver is available commercially as DBeaver PRO and for free as DBeaver Community.
$11
per month per user
MySQL
Score 8.1 out of 10
N/A
MySQL is a popular open-source relational and embedded database, now owned by Oracle.
N/A
Pricing
DBeaver
MySQL
Editions & Modules
Lite Edition Subscription
$11
per month per user
Enterprise Edition Subscription
$25
per month per user
Lite Edition License
$110
per year per user
Enterprise Edition License
$250
per year per user
Ultimate Edition License
$500
per year per user
CloudBeaver Enterprise
$1,000
per year per 5 users
DBeaver Team Edition
$1,280
per year per 1 administrator and 2 developers
No answers on this topic
Offerings
Pricing Offerings
DBeaver
MySQL
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Discounts are available for multi-user licenses.
—
More Pricing Information
Community Pulse
DBeaver
MySQL
Considered Both Products
DBeaver
Verified User
Engineer
Chose DBeaver
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 …
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.
MySQL is best suited for applications on platform like high-traffic content-driven websites, small-scale web apps, data warehouses which regards light analytical workloads. However its less suited for areas like enterprise data warehouse, OLAP cubes, large-scale reporting, applications requiring flexible or semi-structured data like event logging systems, product configurations, dynamic forms.
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.
Learning curve: is big. Newbies will face problems in understanding the platform initially. However, with plenty of online resources, one can easily find solutions to problems and learn on the go.
Backup and restore: MySQL is not very seamless. Although the data is never ruptured or missed, the process involved is not very much user-friendly. Maybe, a new command-line interface for only the backup-restore functionality shall be set up again to make this very important step much easier to perform and maintain.
For teaching Databases and SQL, I would definitely continue to use MySQL. It provides a good, solid foundation to learn about databases. Also to learn about the SQL language and how it works with the creation, insertion, deletion, updating, and manipulation of data, tables, and databases. This SQL language is a foundation and can be used to learn many other database related concepts.
I give MySQL a 9/10 overall because I really like it but I feel like there are a lot of tech people who would hate it if I gave it a 10/10. I've never had any problems with it or reached any of its limitations but I know a few people who have so I can't give it a 10/10 based on those complaints.
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
We have never contacted MySQL enterprise support team for any issues related to MySQL. This is because we have been using primarily the MySQL Server community edition and have been using the MySQL support forums for any questions and practical guidance that we needed before and during the technical implementations. Overall, the support community has been very helpful and allowed us to make the most out of the community edition.
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.
MongoDB has a dynamic schema for how data is stored in 'documents' whereas MySQL is more structured with tables, columns, and rows. MongoDB was built for high availability whereas MySQL can be a challenge when it comes to replication of the data and making everything redundant in the event of a DR or outage.