Likelihood to Recommend 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.
Read full review If you have to manage a lot of different databases from different vendors, you could do well by standardizing on this product. It checks all the boxes for a proper database management studio. You would only have to learn one product to manage them all. However, if you are looking to find a good product for a single database vendor, you might be better off finding a tool that was designed specifically for that vendor product.
Read full review Pros Data import/export and SQL Script generation are quick and simple to do. Fairly intuitive when viewing/editing table data. Ability to save SQL scripts per server and recall them easily. Handy intelligence when writing queries, functions, and stored procs. Read full review Foreign Key Constraint data viewer! This was a tremendously helpful feature that not many other products have. Just pick a constraint and see the data in the child tables! No setup required! Supports any and every database imaginable. Read full review Cons Some icons are kinda small and difficult to understand what they do The spanish translation could be better I think there are many functions that could be useful for me but I don't know what they do Read full review Somewhat laggy performance. Boot up speed was on the slow side and connecting to our database servers was also a little slower than other products. User interface can be a little clunky. Instead of the usual tree view of servers, databases, and schemas, you are presented with lists that you click on and get new windows to pick the new list of data from. Not organized efficiently. Read full review Support Rating 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
Read full review Alternatives Considered 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.
Read full review Compared to Microsoft's SQL Management Studio, Valentina studio was comparable, just harder to get used to in the UI department. It ran slightly slower than other products but did save some time with neat features they baked into the product. However, in using DBeaver Community and DBForge Studio for PostgreSQL from Devart, we found different products that the team ultimately decided to use. DBeaver has all of the features we needed most (minus the constraint data viewer) and a more intuitive UI that we were used to. DBForge Studio for PostgreSQL has a very standard Windows look and feel and lacks some features, like database/table designers, but makes up for those shortcomings in the much easier filtering and sorting options right in the data grids. You can even write a query and edit the data returned, which is something we don't see in many of these tools. Our team ultimately settled on the developers using DBeaver and the support team that needs data viewing/editing capabilities using DBForge Studio.
Read full review Return on Investment 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. Read full review It saved time in some areas of finding child data by not having to write queries to find it. The user interface caused some extra training for some users and ultimately caused them to not like using it. Read full review ScreenShots