DbVisualizer vs. Komprise

Seamlessly querying PostgreSQL/PostGIS, Oracle, SQL Server, and SQLite from one interface without switching tools. The intelligent autocomplete and schema browsing make it ideal for writing queries and understanding unfamiliar databases. Complex performance tuning, deep monitoring, and automated backup/recovery require specialized DBA tools. Performance degrades with tens or hundreds of thousands of rows; command-line tools or ETL solutions are better suited to bulk data processing.

Incentivized

As any other archiving solution, it is very well suited for environments with a large footprint of unstructured data (CIFS / NFS shares for user data) with a large amount of unused/old files and a need to keep those unused files for long term. In our scenario, due to some legal and contractual constraints we need to keep these files for 15 years. Archiving is a good choice to move the unused files to a cheaper storage tier, both on-prem or cloud.

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.

• It gives you a good overview on user data: files age, sizes, file types, owners, etc.
• It is very flexible on the archiving policies.
• The data scans are really fast without affecting storage's performance.
• It has a great alternative to STUB files, which they call 'bread crumbs' (symlinks to files).

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)

• Its licensing plan, which takes into account the amount of data analyzed instead of data transferred.

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

It does what we need it for, which is manipulate data, check connections, visualize database structures, check on user rights, or even just version checks on the used databases. The 'type to get to table name' feature is often irrational in behaviour, which leads to frustration. The start-up time could be much better, and the UI changes between versions are sometimes a hassle for us when buttons are suddenly moved or their appearance changes. We use a wide variety of DBVis versions on customer installations (which use the once-bought version), and differences in the look and feel between versions sometimes slow us down.

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

We have used Veritas Enterprise Vault in the past, and besides its being a well-known player on the data archiving market, their tool is far more complex to implement, to manage and to keep working. Komprise is very robust and also very easy to implement, as most part of the job is done on Komprise side. The management console is delivered through a public URL as a SaaS platform. You only need to deploy a few VMs for scan/archiving/user access, which they call "Observer VMs." Komprise also doesn't uses Stub files, which is a poor implementation adopted by the competitor for file access. We had a lot of issues in the past with stub files. Komprise has implemented 'bread crumbs', which are CIFS symlinks to the files on the Observer. It is a very good implementation and it works really well.

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

• It allowed us to free up some space on our main storage during a time where we didn't have the budget to expand it.
• It allows us to move unused data to a cheaper storage tier (Azure Blobs).

Incentivized