DbVisualizer vs. Eclipse vs. PhpStorm

DbVis is our tool of choice when we need to work with a wide variety of Db vendors and versions. It allows us to replace several proprietary tools for accessing and, in part, managing database systems. It gives our customers and us a single base to work on databases. No need for us or them to install, learn, and pay for multiple solutions. If one would, for example, use ONLY one dbms, e.g., PostgreSQL, then DBVis could be a bit of an overkill.

I think that if someone asked me for an IDE for Java programming, I would definitely recommend Eclipse as is one of the most complete solutions for this language out there. If the main programming language of that person is not Java, I don't think Eclipse would suit his needs[.]

Incentivized

PhpStorm is well suited for any project that utilizes PHP. I have used it on Windows, Ubuntu, and Mac OS and it works great on all those platforms. Having a solution that keeps the developer from having to constantly switch tools to do their job is invaluable. Whether you're a junior developer, front end engineer or a senior developer, PhpStorm is a great product that will help you get your work done.

Incentivized

• Out-of-the-box support for many different databases.
• Intuitive UI for interacting with data.
• Flexibility of SQL Commander for writing scripts.
• Great support for working with JSON data in recent updates.
• Database connections over SSH.
• Table relationship visualization is very helpful.
• The tree view is well organized in how it splits out schemas.

• Eclipse organizes imports well and does a good job presenting different programming languages.
• Eclipse auto formats source code allowing customization and increased readability.
• Eclipse reports errors automatically to users rather than logging it to the console.
• Eclipse has coding shortcuts and auto-correction features allowing faster software development.

Incentivized

• Database browsing, Remote host browsing, and all the deep seated customizations for both the UI and Technical feasability are the result of an amazing integrity and compatibility with most components and technologies.
• The built-in shell is insanely helpful for traversing code in order to debug scripts with ease, and the plug-in system makes this software quite extensible.
• Not to mention the variety of options and settings (divided into global settings and per-project settings) are both intuitive & easy to use, especially the fact that I can export and import them across my workstations while maintaining my spacing & indentation, highlighting, inspection patterns and syntax styling.

Incentivized

• Small, but noticeable: it would be nice to be able to highlight just one column of a data output for copy/paste by clicking on the column header (a feature some of us are accustomed to from SQL Server Management Studio)
• Is there an ability to bulk import an excel file to a table in a connected SQL Server in DbVis? If so, I haven't figured that out yet. I still largely use Microsoft SSMS to import data to our team's personal SQL Server, but can easily query that server via DbVis)
• (I really don't have any major complaints - our company has tried to steer users toward DBeaver for YEARS, which I cannot stand. DbVis knocks the beaver out of the water)

• While the DB integration is broad (many connectors) it isn't particularly deep. So if you need to do serious DB work on (for example) SQL Server, it is sometimes necessary to go directly to the SQL Server Studio. But for general access and manipulation, it is ok.
• The syntax formatting is sometimes painful to set up and doesn't always support things well. For example, it doesn't effectively support SCSS.
• Using it for remote debugging in a VM works pretty well, but it is difficult to set up and there is no documentation I could find to really explain how to do it. When remote debugging, the editor does not necessarily integrate the remote context. So, for example, things like Pylint don't always find the libraries in the VM and display spurious errors.
• The debugging console is not the default, and my choice is never remembered, so every time I restart my program, it's a dialog and several clicks to get it back. The debugging console has the same contextual problems with remote debugging that the editor does.

Incentivized

• Some of the newest github copilot features lag behind what's being done in vs code and would be nice if more of the newer features were brought over though this has greatly improved recently
• Interface can be a little overwhelming for newcomers
• Some features like rainbow brackets should be native rather than addon

Incentivized

We never had problems with it. It is able to connect to all data sources (Oracle, Informix, DB2, SQL Server) that we currently use.

Incentivized

I love this product, what makes it one of the best tool out in the market is its ability to function with a wide range of languages. The online community support is superb, so you are never stuck on an issue. The customization is endless, you can keep adding plugins or jars for more functionalities as per your requirements. It's Free !!!

Incentivized

I use this tool for several hours each day, spanning many years in various projects. It's wide support for various database types while keeping consistency within the UI for each is important when working with various databases day in and day out.

It has everything that the developer needs to do the job. Few things that I have used in my day-to-day development 1. Console output. 2. Software flash functionality supporting multiple JTAG vendors like J-LINK. 3. Debugging capabilities like having a breakpoint, looking at the assembly, looking at the memory etc. this also applies to Embedded boards. 4. Plug-in like CMake, Doxygen and PlantUML are available.

Incentivized

PhpStorm is very easy to use, once you get the hang of it. It can take a while to get the hang of it because there's so many options, some of which are buried in the imposing settings panel. It could use some help with multi-cursor, especially multi-file editing but that's a minor gripe.

Never used

Incentivized

I gave this rating because Eclipse is an open-source free IDE therefore no support system is available as far as I know. I have to go through other sources to solve my problem which is very tough and annoying. So if you are using Eclipse then you are on your own, as a student, it is not a big issue for me but for developers it is a need.

The JetBrains community is all about helping others succeed, even in the most obscure setups. I have never had a question go unanswered, or I have never been able to come up with empty results in searching for the answer. My questions or concerns are typically address from other users in the community, so timing is pretty quick for a response

Incentivized

[DbVisualizer] is pretty easy to use compared to IntelliJ because of it's simplicity. The performance is very good, it feels as good as a native application compared to the other two softwares I used for the same purpose. It's very cheaper compared to the other two tools and that's a big selling point.

Incentivized

The installation, adaptability, and ease of usage for Eclipse are pretty high and simple compared to some of the other products. Also, the fact that it is almost a plug and play once the connections are established and once a new user gets the hang of the system comes pretty handy.

Incentivized

Easier to use, more features, more reliable. Much more purpose built with specific integrations aimed directly at php code instead of the broad generic interfaces the other software have that are aiming to support many different languages.

• Positive: Real time saver when working across multiple databases. At least 30-40 mins a day are saved
• Positive: Helpful for the 'quick DBA' tasks without switching to the native tools: approx 1-2 hours saved weekly
• Positive: Easy switch between environments / schemas / etc without hassle: saved at least an hour daily

• This development environment offers the possibility of improving the productivity time of work teams by supporting the integration of large architectures.
• It drives constant change and evolution in work teams thanks to its constant versioning.
• It works well enough to develop continuous server client integrations, based on solid or any other programming principle.

Incentivized

• PhpStorm decreased the time to market of new features - we are following the Agile SCRUM methodology with 2 weeks sprints. Using PhpStorm helped with releasing UI features even faster than 2 weeks.
• Considering the price of the license and the cost of the server where we run it, the ROI is still high due to less time spent by developers with writing code, debugging, refactoring etc. Especially when you have highly paid developers.
• Increased people's happiness - by using a modern tool with lots of features which has made their work easier.

Incentivized