DbVisualizer vs. Sequel Pro

Well suited for medium size to large Oracle system that includes a large and complex database schema with many database objects including functions and triggers. Also well suited for a medium size to large Microsoft SQL Server system with many complex database objects. Its SQL editor and query builder are well suited in developing complex SQL queries.

• Super easy for quick development and investigation
• The interface of exporting tables to SQL can be made better, it's not easy to manually check
• Not suitable for designing your DB
• Connections over SSH to vagrant and Docker hosted DBs
• Auto suggestion can be better

Incentivized

• Provides simple access to all tables, indexes, views, triggers, stored procedures, etc., to just about every database on the market
• Allows me to develop and run queries in a simple, easy to read and understand manner
• Allows me to create entire new schemas as well as alter existing schemas
• Gives me access to databases without the need to install specific drivers for any particular database

Incentivized

• Editing existing data. Editing record contents is trivial in Sequel Pro, while not nearly as easy in MySQL Workbench or phpMyAdmin.
• Deleting data - even simpler than editing data.
• Inserting new data - using "Duplicate row" then making needed changes is very simple.

Incentivized

• does not handle lost connections well (specially after stopping a running query) (mysql). eg. after hitting stop, and then hitting run again, it can sometimes look like its running the query, but it isn't actually!
• filtering on databases window is clunky (why the need for filtering certain object types at a time? just filter everything, google style)
• altering table, adding columns (NOT to the end of the table's columns, but earlier) is not supported (mysql) even though the db supports it (alter table add column BEFORE..)

Incentivized

• Improving the way we create new connections to remote databases
• I couldn't find any way to configure my local server (MySQL), so I need to make changes on server outside the application. I know that there are other tools that integrate it, so you don’t have to leave the workflow
• It could have a feature to integrate our databases or connections (favorites) with other devices, like using Google Drive or Dropbox. It would be really useful!

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.

Never used

Incentivized

It's open-source and very convenient to work with. I can easily import any database I want using a data dump and runt the queries on them to derive the data insights on the data. I might want to use Excel to visualize that, that might be one of the disadvantages.

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

MySQL workbench is good to work with MySQL databases, but Sequel Pro gives us the ability to work with any SQL databases. It's open-source, lightweight and solves the problem that I am required to solve to run the DDL and DML queries.

Incentivized

• The only point I could potentially give is hours saved by having so many warehouses hooked up in one place vs. having to manage connection string changes/password updates across multiple applications... maybe 10% decrease in time spent managing connections? Mind you, I've had everything hooked up on DbVis for close to 6 years so it's hard to remember the "before times"

• Unreliability has lead to wasted time and frustration among staff.
• The ease of testing database changes and modifying test data WHEN IT WORKS theoretically makes testing quick and easy but in reality, this is far outweighed by the wasted time and frustration involved with it not being reliable.
• The ease of seeing the relations between tables is very nice and saves time when trying to see how unfamiliar tables are connected.

Incentivized