DbVisualizer vs. SQL Server Management Studio (SSMS)

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

It's well suited for database management, backups, data import/export. It's not as strong for handling multiple queries at the same time, as a developer, we sometimes have multiple queries opened on the development database. In SSMS if you close the software, you'll lose the opened tabs and history

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.

• Easy and clean IU that enables quick analysis
• Reliable and with known stability
• Folder like managment of Databases/Tables

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)

• it can still be made easier for connecting perspective
• some bugs on versions of SQL can be avoided.
• can be more user friendly

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.

It's very user friendly. If you know T-SQL then you can use this. Really even if you don't it's not that hard to figure out. You can create things visually as well.

Incentivized

Never used

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

It still lacks some features that make DataGrip great for developers like tab history, persists the last session, detailed customization for query formatting, more data export options and the table edit dialog is more comfortable to use since it can be resized

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

• Not expensive
• Easy to install and distribute from Windows
• Not complex (Low trainning)

Incentivized