DbVisualizer vs. Rocket Mainframe Application Testing and Debugging

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

• 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

• 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)

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.

Never used

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.

• 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