DbVisualizer vs. Python IDLE

Whenever you have to access data sources from more than one database engine provider, you should consider using DbVisualizer for the task. Switching between multiples IDE consumes time and resources (memory), and you also need to learn menus, shortcuts, etc., for each IDE, while using DbVisualizer allows you to work consistently no matter which database engine you are connecting. You can use it to simply navigate through data structures, write SQL sentences or even create new tables and views, develop stored procedures, etc.

Incentivized

Scenarios where python IDLE is well suited 1-Quick scripting and prototyping 2-Education and training 3-small projects utilities 4-exploring python libraries and modules Scenarios where python is less appropriate 1 large scale projects 2 complex debugging and profiling 3 multi language development 4 Advanced code analysis and inspection

• Timed queries that add their result to the result grid for every execution are helpful. Creation of graphs also extremely helpful.
• Query history and auto-recover feature makes sure we don't lose our queries.
• Actions like exporting grids to Excel or other tools is a very easy task.

Incentivized

• Firstly, I would say Python IDLE interface is user friendly.
• Easy to learn for the beginners.
• Syntax highlighting is nice features.
• Smart indent helps a lot.

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)

• 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 find it very user-friendly, everything is easily viewable and the fact that I can move modules around and customize the colors and appearance of things really helps make it more usable. I also find the default keyboard shortcuts intuitive and the in-program descriptions are easy to follow and understand.

Incentivized

The IDE Python IDLE is a good place to start as it helps you become familiar with the way Python works and understand its syntax.

This IDE allows you to configure the environment, font, size, colors, .....

It also looks like any simple text editor for any operating system, I work with Windows or Linux interchangeably, and you don't have to learn to use the IDE before programming.

Once the IDE is executed you can start programming directly in it.

Incentivized

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 provides a good value when compared against other 3rd party products with similar features as well as products with similar functionality made by the database vendors. The user interface is good and user friendly / intuitive and easy to learn. It doesn't take too long for an experienced DBA / database developer to come up to speed.

It's easy to set up and run quick analysis in Python IDLE on my local machine. The output is direct and easy to read. But sometimes I prefer Jupyter Notebook when the datasets are large, since it would take too long to run on my local machine. It is easier to run Jupyter Notebook on my cloud desktop

Incentivized

• 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

• 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