DBeaver Reviews & Insights

I use DBeaver every single day as a data engineer. I use it to navigate though the database and to create tailored reporting for needs of the organization.

I enjoy DBeaver even with the crashing. So for large queries with several CTEs I wouldn't recommend. However for normal ease of use for Database querying I would recommend it.

I use DBeaver to connect to remote databases and explore and manipulate data when needed

Connecting to remote databases, exploring table and understanding the schema is easy with DBeaver

DBeaver is used to connect, query, update and manage a variety of databases through many configurations. I personally use it because it can store many queries and associate them with a particular database or on a particular sheet with related queries. It can make diagnosing problems much more quickly than without organizational features.

DBeaver is very well suited to general purpose DB interaction, adhoc querying, for complex setups. It does need some time to learn and come up to speed.

DBeaver is used by me to work with SQL Server databases.

It is the perfect sidekick for every day's database work with SQL Server (I guess with other databases as well). Whether you need to browse data, import/export, alter database objects, compare objects, view automatically generated database diagramas, and so on. I regret every day I spent using SSMS without knowing this tool existed.

We use DBeaver to connect to our Snowflake instance, as well as our on-premises Microsoft SQL servers. It is very nice because we can query both without having to have an application for each. I find that DBeaver is able to generate the DDL behind Snowflake views much easier than in the Snowflake IDE.

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.

I use DBeaver as a graphical interface for accessing databases locally and remotely for testing and data analysis. It allows easy access to viewing data and running SQL Queries against the data as well as updating test data locally.

DBeaver does a lot and has a lot of features, especially for free. Sometimes this amount of features makes the UI tricky to navigate and sometimes it will take more time to get to the place you want to get to. I wouldn't recommend DBeaver for beginners as it may overwhelm them. Still, you can't beat how much control it gives you.

DBeaver is used by our company as a go-to application to access data and manage relational databases. It is used across multiple departments and addresses the need to conveniently and easily access, read and manipulate the data. Due to its simplicity and at the same time broad functionality, it is successfully used by both technical and non-technical categories of users.

DBeaver is a great all-in-one database tool that would be well suited for any user that requires accessing or modifying data in any of the common database types. Its broad functionality and, at the same time, ease of use make the application easy to use for users of any technical level - from application developers to QA engineers to business analysts.

DBeaver is used by both software developers and people who are responsible of support services for a web application with large user base. It allows developers to quickly view and modify database as they are developing the application and testing features. For support people it helps to solve customer queries which need to get information from the database. They also use it to modify database when configuration options for the application needs to be changed.

It's really suited for any scenario related to database management. That includes both viewing the database and making changes. It beats doing things from the command line in every way and helps to avoid doing mistakes because doing things from UI is much more intuitive. Supports large amount of different database vendors.

A lot of developers use DBeaver for its ease of use. It lets me as a developer do a lot more than a typical SQL client. I especially like the visualization that this tool offers to me. I can easily see how all the tables are connected in an ER diagram and I can make changes and modify it.

For read-only work in dev, I highly recommend it. It will save you time especially with its autocomplete features and ease of use. To modify the data and work in the prod environment I would stay away from this open-source tool. It will still get the work done but you might encounter some issues.

Its really great to view and manage data in development, staging, and even production databases. DBeaver supports any SQL database nicely, we are using three different kinds of SQL databases (MySQL, PostgreSQL, and SQL server) and I don't need multiple database client tools since all of them could be handled with DBeaver. By doing that, I save a lot of time and PC resources viewing all of the databases we have, which is really great.

Really good if you have a lot of databases to connect to. Especially if most of them are different types of databases. However, if you only use one type of database, there are other options that might be better suited for your needs since the functionality will be focused on that particular database type.