view counter


Oracle PL/SQL (Procedural Language/Structured Query Language) resources, news, and support articles.

MySQL 5.0 migration bug

At present, you can’t use the MySQL Workbench migration tool to migrate MySQL 5.0 to MySQL 5.5, as documented in Bug 66861. The documentation of the mysql.proc table is also different from the physical definition in MySQL 5.0 release. I logged documentation Bug 66886 to get it fixed.

Truncate dangers

Click the image for scripts

September Update at the PL/SQL Challenge

[Find below the text of the September 2012 e-newsletter sent out to PL/SQL Challenge subscribers.]

Another summer gone...and a hot one it was. Let's just hope the ice in the
Arctic circle returns next year. In the meantime, eyes turn towards Oracle Open
World, the annual extravaganza of All Things Oracle (and that is an
awful lot of "things", compared to the old days).

Conditional integrity

Click the image for scripts
Inspired by Vincent Malgrat’s answer to a question about this

Bulk Transfer Still Fails

As many already know, I’ve been trying to get the MySQL Workbench migration feature working between Microsoft SQL Server 2012 and MySQL 5.5. There are a number of features added to the point release, and one led me to believe that the Migration tool expects to find the data in a schema of its own, as opposed to the dbo schema. Having made that change in Microsoft SQL Server, it did appear to have a positive impact on the migration.

Setup SQL Server Schema

After you’ve installed Microsoft SQL Server 2012 and created a database schema, you still need to setup or configure the database schema. That means you must grant permissions to a user to work in the database schema, otherwise you get the following type of error message.

Trying to Migrate Data

Getting the MySQL Workbench’s Database Migration has been interesting, and at present incomplete. While I can now successfully connect to the SQL Server 2012 source database and capture a schemata list, migrating the data from SQL Server doesn’t work. Actually, the connection doesn’t work without modifying a Python library in the current MySQL Workbench release.


You must install and then configure a Windows Data Source Name (DSN) for SQL Server’s ODBC before you can connect MySQL Workbench to a SQL Server and migrate data.

view counter