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
Visual Studio
Score 8.6 out of 10
N/A
Visual Studio (now in the 2022 edition) is a 64-bit IDE that makes it easier to work with bigger projects and complex workloads, boasting a fluid and responsive experience for users. The IDE features IntelliCode, its automatic code completion tools that understand code context and that can complete up to a whole line at once to drive accurate and confident coding.
dbForge Studio has a more intuitive UI for die-hard Windows users. It's also easier to use sorting and filtering in their grids. However, that one lacked the script generation and schema editing tools our development team needed to use on an almost daily basis.
While Visual Studio Code makes up for some of its shortcomings by being an IDE for just about any language you want to develop in, having a designer for WPF or Windows Forms saves a ton of time. However, Code provides better intellisense for CSS when you use SAAS (SCSS).
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.
It's useful for app development, debugging, and testing. I've been using it for two years and have seen it grow into a fantastic tool. All of the features, NuGet packages, and settings that enable different types of projects are fantastic. It also has a connection to Azure DevOps and Git. It's a fantastic product that's simple to use.
Since Microsoft offers a free Community Edition of the IDE many of our new developers have used it at home or school and are very familiar with the user interface, requiring little training to move up to the paid, enterprise-friendly editions we use.
The online community support for Visual Studio is outstanding, as solid or better than any other commercial or open-source project software.
Microsoft continuously keeps the product up to date and has maintained a history of doing so. They use it internally for their own development so there is little chance it will ever fall out of favor and become unsupported.
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.
Certain settings and features can sometimes be challenging to locate. The interface isn't always intuitive.
Sometimes there are too many ways to do the same thing. For example, users can quickly add a new workspace in Source Control Explorer when a local path shows as "Not Mapped," but it doesn't indicate that the user might want to check the dropdown list of workspaces. The shortcut of creating a new workspace by clicking on the "Not Mapped" link can lead to developers creating too many workspaces and causing workspace management to become unwieldy. If the shortcut link were removed, the user would be forced to use the Workspace dropdown. While it can add an extra step to the process, workspaces would be managed more easily, and this would enforce consistency. At the very least, there should be a high-level administrative setting to hide the shortcut link.
VS is the best and is required for building Microsoft applications. The quality and usefulness of the product far out-weight the licensing costs associated with it.
The thing I like the most is Visual Studio doesn't suffer from Microsoft's over eager marketing department who feel they need to redesign the UI (think Office and windows) which forces users to loose large amounts of productivity having to learn software that they had previously known.
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
Between online forums like StackOverflow, online documentation, MSDN forums, and the customer support options, I find it very easy to get support for Visual Studio IDE when I need it. If desired, one can also download the MSDN documentation about the IDE and have it readily available for any support needs.
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.
I personally feel Visual Studio IDE has [a] better interface and [is more] user friendly than other IDEs. It has better code maintainability and intellisense. Its inbuilt team foundation server help coders to check on their code then and go. Better nugget package management, quality testing and gives features to extract TRX file as result of testing which includes all the summary of each test case.
We've had hundreds of hours saved by the rapid development that Visual Studio provides.
We've lost some time in the Xamarin updates. However, being cross platform, we ultimately saved tons of time not having to create separate apps for iOS and Android.