DBeaver vs. Komprise

If you are connecting to Snowflake and want to query from your laptop, I find that this is much easier to use than Snowflake's IDE. It allows us as a business intelligence team to more easily connect to our servers, and code with much less hassle. It would be less appropriate if you are only on an on-premises SQL server, in that case, I would just use SSMS.

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

• Data import/export and SQL Script generation are quick and simple to do.
• Fairly intuitive when viewing/editing table data.
• Ability to save SQL scripts per server and recall them easily.
• Handy intelligence when writing queries, functions, and stored procs.

Incentivized

• 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

• Some icons are kinda small and difficult to understand what they do
• The spanish translation could be better
• I think there are many functions that could be useful for me but I don't know what they do

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

Incentivized

Not a lot of users have DBeaver so fewer resources are available online to help you if you have any issues. When I was trying to figure out how to create my own ER diagrams, it was a little tough to find resources

Incentivized

MySQL workbench from MySQL only supports MySQL databases and it only provides basic functionality. On top of that, the user experience could be quite confusing for first-time users. SSMS from SQL server doesn't support inline editing nicely. The view for inline editing and view data is different, making it uncomfortable to use. All in all, DBeaver is the best tool when you manage a lot of databases with different types.

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 Ability to manage DBeaver and query ad-hoc quickly
• By having the queries saved it has saved developer time and thereby increased the ROI on the investment on the tool
• This has made firefighting quicker and freed up resources for more development work.

Incentivized

• 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