When comparing dbMigration .NET vs MySQL Workbench, the Slant community recommends MySQL Workbench for most people. In the question“What are the best relational database migration tools?” MySQL Workbench is ranked 3rd while dbMigration .NET is ranked 11th. The most important reason people chose MySQL Workbench is:
Actions can be directly carried out on tables. The software prepares the relevant query for approval before execution.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Supports multiple databases
Lots of databases supported.
Pro Migrates data
Pro Portable
Portable version.
Pro Easy to use
Actions can be directly carried out on tables. The software prepares the relevant query for approval before execution.
Pro Community version
There is a community edition available that is free and open source; licensed under GPL.
Pro EER diagramming
MySQL Workbench has enhanced entity–relationship modeling support.
Pro Cross-platform
Works on Windows, Linux, OS X.
Pro Database synchronization
Forward & reverse engeneering
Cons
Con Limited free version
Free version is limited to 10000 rows per table.
Con Chaotic website
The website gives a bad impression of an otherwise impressive product.
Con Mixed experience
Doesn't support HiDPi mode on Windows, everything looks blurry. On Linux it has missing features. On Mac seems to be working just fine. But overall a mixed experience.
Con Unintuitive UI
Workbench's user interface is regarded by a lot of users as unintuitive and hard to use.
It seems cluttered and hard to get used to. The left side of the application has several sections (which you get to choose which to open) with several tools for each. A lot of features are hidden behind menus and need some getting used to find them.
Con Freezes constantly
Running any kind of query with more than a thousand records or even just opening a file and other actions crashes the application. You are unable to actually stop a query. You have to kill from Windows Task Manager every single time.