With the release of Webyog's flagship product, SQLyog Enterprise version 4.1, a new ODBC "Power Tool" is introduced that replaces the old "ODBC import tool."  Starting with SQLyog version 4.2 it was re-named "SQLyog Migration Tool," so this is the term that I will use in this text.  This is not just a new name for something old that comes in a new bottle--the Migration Tool has been completely rewritten. It is all completely new code, but – more important to users – it offers a wide range of new possibilities. The term "ODBC-import" to me means, "Fetching some external data into MySQL."  "Migration" is much more than that – it imports not only data but also indexes ("ordinary" indexes, Primary Keys, Foreign Keys – all that used to be called "metadata"), and it provides a large set of options for (almost) any situation.

It is equally well fit for use with a Migration Process considered as a one-time event (no matter how long that process might take!) and in situations with "permanent coexistence" (or "permanent migration" if you like) of more database systems within an organisation.

In my opinion the SQLyog ODBC-import tool is the most complete, versatile, intuitive and flexible import tool that exists and that you can imagine. All the options, that the tool offers, are available from the SQLyog GUI. There is no need to edit some 'strange format' file to transform or filter data during import. It lets you easily import any subset ("vertically" or "horizontally") of data and metadata (all sorts of indexes). It can be scheduled, run from external applications, and run in batch-mode in combination with any other OS/system command, executable file and any other job type of the SQLyog Job Agent (SJA).  The other job types offered by the SJA are, MySQL to MySQL synchronization, High Performance Scheduled Backups and "Notifications Service" – the last one is a very unique facility that lets you schedule and execute any SQL with your databases and have formatted result-sets of these queries delivered to your mailbox.

The XML-format of the job file control lets you integrate the full functionality of the ODBC-import tool (and any other job type of the SJA) into your own applications, if that is what you want.

If all of that talk is nonsense to you, you can simply use Migration Tool from the SQLyog GUI, and it is almost as simple as using an Office-suite application.  The wizards will guide you so you will not have to worry about what a complicated thing you actually are doing!

SQLyog has developed terrifically over that last year or so, and it continues to do so.  Before this article is out you will probably see that full support for MySQL version 5 features (Stored Procedures, Triggers and Views) is available, and in just a few weeks more you will have localised versions.  Check the Webyog website frequently at www.webyog.com.  Moreover, do not forget that the Migration Tool is only a "small corner" (though big in itself!) of the complete set of functionalities you will find in SQLyog Enterprise.  I recommend that you download the fully functional demo of SQLyog Enterprise from www.webyog.com if you do not have it, so that you can experiment with it on your own system.  This article should give you ideas enough for many hours of experimenting and testing for yourself.

The content of this article will be:

• Introduction (you just read it!).
• Getting Started.  Here we take the "easy approach" to migration to MySQL.
• Methods used and applied by the Migration Tool.
• What's New.
  • ODBC-import with SQLyog is now implemented in the code of the SJA (SQLyog Job Agent).
  • It will now import not only DATA but also METADATA.
  • It offers a wide range of general options for the import.
  • It offers various options to transform data during import and options for filtering of which data should be imported.
  • It implements a "trigger" or "write-back" functionality.
  • A notifications' feature similar to the SQLyog/SJA "Notifications Service" has been implemented with the new Migration Tool.
• What to use the Migration Tool for?
  • Migration to MySQL (as the name of it says!).
  • (More or less) permanent coexistence of MySQL and other databases within an organisation.
• MySQL and MySQL – a note on how to use the Migration Tool across different MySQL versions.
• Conclusion.
• About the author.