MySQL Workbench 5.2.41 GA + Migration Wizard Available

The MySQL developer tools team announces the availability of version 5.2.41 of the MySQL Workbench GUI tool. This version has significant improvements in several parts of the tool and also includes the new Migration Wizard plugin.

The new Migration Wizard presents an easy to use GUI for migrating databases from third party products to MySQL. In this initial release, support for Microsoft SQL Server is included, in addition to other products that support ODBC, such as PostgreSQL.

Other improvements include:

  • More than 100 bug fixes
  • Code completion in the SQL Editor (beta)
  • Better handling of schema synchronization in modeling
For a full list of issues fixed in this release, see

Please get your copy from our Downloads site.

Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

Workbench Documentation can be found here.

Utilities Documentation can be found here.

If you need any additional info or help please get in touch with us.

Post in our forums or leave comments on our blog pages.

– The MySQL Workbench Team

Author: Mike Lischke

Team Lead MySQL Workbench

9 thoughts on “MySQL Workbench 5.2.41 GA + Migration Wizard Available”

  1. Just tried the Migration Wizard. I am attempting to use ODBC interfaces to migrate MS Access (.mdb) data to MySQL. Unfortunately, it can’t do more than connect to source and target databases. When it tries to reverse engineer the selected schemata, it crashes. It did the same thing with 3 different databases.
    This is too bad because the old migration assistant provided with MySQL GUI Tools could migrate Access tables and data beautifully. I was hoping the new assistant might even be able to migrate queries, but apparently not yet.

  2. I installed version for Ubuntu 12.04 x64 and shortly after starting workbench jbd2 constantly kept over 98% I/O usage. After closing workbench, jbd2 I/O usage dropped to 0%. The same situation repeated next time. Afterwards I reinstalled 5.2.40.

  3. Thanks for the update!

    I would like to request a way to turn off code complete. It would be awesome if it was an option on the connection.

    The reason:
    (I make an assumption here on how its done.) I have used other tools that load the schema from information schema. This puts a load on the server and has caused locks and other unintended consequences.

  4. In 5.2.41 sometimes I’m not able to edit a table in the diagram, neither by double clicking nor by using ‘Edit Table’ context menu item. The bottom module with table data and column will not open. After several attempts to open other tables for editing the program crashes. After restart I can edit the tables but after a while the problem comes back. It’s very problematic and I’m back to 5.2.40.

    Strangely, 5.2.41 wanted to change most index names in all my tables saying that mysql 5.5 doesn’t allow same index names as constraint names. That’s weird because I have many databases created with versions prior to 5.2.41 that have many identical index and constraint names and they work fine on various versions of mysql 5.5 without any problem. At least Workbench could provide some more explanation or provide a link to documentation so that I could understand what’s going on because this doesn’t prove to be right based on my experience with mysql 5.5.

Leave a Reply