Sequel Pro vs. SqlDBM

• 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

• 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

• 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

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

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

• 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