dbForge Studio (Edge) vs. Sequel Pro

Whenever a user or DBA wants to compare schematics between two environments, dbForge is extremely helpful. This is useful during version or framework upgrades, a database upgrade, patch implementations, service package implementations, or any time to environments would be different. The time it would take to write and execute queries, and then compare is exponentially longer than it takes with dbForge, where this is done and you have an application that allows you to quickly identify incongruities.

Incentivized

• 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

• Compare entire or subset of MySQL tables between databases
• Configure comparison rules
• Sync data between compared databases depending on differences
• Save comparison rules for reuse and sharing
• Break down differences between missing/new records, or different records
• See differences highlighted per field
• Execute sync immediately, or save as an SQL script file
• Command-line tool that can be used to add comparisons to deploy scripts

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

• [The] installation error I've already reported (ABARTN).xml [could use some improvement]. This has to do with Windows Defender (the default Windows anti-virus) not allowing the installation on the default installation directory of dbForge Studio [for SQL Server], thus the error. [With] the workaround, [I] was to disable the anti-virus for the duration of the installation, then turn it back on when the installation [was] been completed.
• [I would like to see] better defined licensing models for larger teams (seated vs. name licenses).

• 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

Although experience here is limited, as only one question has been asked and answered promptly, the registration and licensing process was very smooth and professional. There are forums online that discuss dbForge issues, as well as a Facts and Questions section on dbForge's website, so product support does seem to exist if needed.

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

I would say that dbForge equals or beats most of the abilities of the other tools I evaluated at the time. dbForge had better support (Devart), and regular feature updates. dbForge has better tools for data comparison and import/export. The price tag is slightly higher, but renewals rates are pretty good. It's a quality tool that still is well worth the cost.

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

• We perform better and faster syncing analysis between databases.
• We update running mysql databases faster and more efficiently.
• Especially with MySQL Workbench we had immense irritations due to all the crashes during the day. With dbForge Studio we finally had a power tool which is stable and does not crash constantly.

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