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[.]
User interface is easy to use, and in some ways better than Toad. The left hand side shows all databases, and you can drill down to instance, storage, schemas, tablespaces, and performance views. The right hand side displays the details of the selected object.
This is the best tool if you want to manage multiple RDBMS platforms in a single tool using the same familiar interface. Other third party tools can do it also, but it's not nearly as integrated as this, and may require additional plug-ins installed. DBArtisan excels at this, and can perform cross-platform data migrations easily.
It has different DB analysts, which can help diagnose issues with performance, optimize storage, detect fragmentation, and plan for capacity growth. For almost any action you want to take, you can generate the DDL for preview, and/or schedule it to run at a specific time.
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.
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 !!!
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.
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 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.
It has a positive ROI on our organization. It's better than OEM and SQL Developer. Although the license could be expensive, it is perfect for large organizations, especially with multiple RDBMS platforms.
Most features are redundant between DBArtisan and Toad. I would not recommend using both if you already own one of them. Just download the trial for the one you're not using, and see what works best for your organization.
DBArtisan is great for DBAs and would be my personal preference. Toad is good for developers and DBAs alike but I feel like sometimes the interface is too busy and too clumsy to use.
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.
