DbVisualizer vs. Python IDLE

Well suited for medium size to large Oracle system that includes a large and complex database schema with many database objects including functions and triggers. Also well suited for a medium size to large Microsoft SQL Server system with many complex database objects. Its SQL editor and query builder are well suited in developing complex SQL queries.

IDLE is a good option to run small scripts directly on the console, and that's it. It is a good exit when you don't want or need to open a proper IDE like Pycharm.

Incentivized

• Provides simple access to all tables, indexes, views, triggers, stored procedures, etc., to just about every database on the market
• Allows me to develop and run queries in a simple, easy to read and understand manner
• Allows me to create entire new schemas as well as alter existing schemas
• Gives me access to databases without the need to install specific drivers for any particular database

Incentivized

• The best thing is the debug that incorporates.
• Friendly graphic environment.
• Provide keyword auto-fill.
• Color the command syntax automatically.
• Very configurable.

Incentivized

• does not handle lost connections well (specially after stopping a running query) (mysql). eg. after hitting stop, and then hitting run again, it can sometimes look like its running the query, but it isn't actually!
• filtering on databases window is clunky (why the need for filtering certain object types at a time? just filter everything, google style)
• altering table, adding columns (NOT to the end of the table's columns, but earlier) is not supported (mysql) even though the db supports it (alter table add column BEFORE..)

Incentivized

• Too simplistic
• Could not find source revision management integration support
• Only basic debugging is available
• Does not have data-science-specific notebooks (but can be installed separately)

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 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.

1-Ease of use: python IDLE is relatively ease to use,especially for developers familiar with python. Its simple and intuitive interface makes it easy to navigate and find basic features 2- learnability:python IDLE is relatively easy to learn especially for developers with prior experience with python or other programming Languages 3- efficiency: Python IDLE efficiency is limited by its basic feature set and lack of advanced tools.while it’s great for rapid prototyping and small scale developers

Never used

Incentivized

Python IDLE support is what the community can give you. As it is free software, it does not have support provided by the manufacturer or by third-parties.

In any case, for most of the problems that normal users can find, the solution, or alternatives, can be found quickly online.

As this IDE is made in Python, the support is the same group of Python developers.

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

I chose python IDLE for its simplicity and ease of use, which made it ideal for rapid prototyping and small scale development future sets: while python IDLE offers a basic set of features, including syntax highlighting, auto completion and basic debugging tools Performance :python IDLE is relatively lightweight and doesn’t require significant system resources, making it an excellent choice for older machines or resources constrained environment

• The only point I could potentially give is hours saved by having so many warehouses hooked up in one place vs. having to manage connection string changes/password updates across multiple applications... maybe 10% decrease in time spent managing connections? Mind you, I've had everything hooked up on DbVis for close to 6 years so it's hard to remember the "before times"

• In a short time, we were able to develop several ML models for various teams to make accurate decisions.
• Beginners can easily understand and adapt to GUI.
• We could automate several manual validation tasks and so could reduce human intervention.

Incentivized