Bug #37450 Cannot change schema name when migrating Access databases
Submitted: 17 Jun 2008 15:34 Modified: 19 Oct 2009 11:26
Reporter: Chris Wilson Email Updates:
Status: Won't fix Impact on me:
Category:MySQL Migration Toolkit Severity:S3 (Non-critical)
Version:1.1.12 OS:Any
Assigned to: CPU Architecture:Any
Tags: CHECKED, mysql migration access schema name

[17 Jun 2008 15:34] Chris Wilson
We have Access database files named like this:

CAMFED Data 3 Ghana 220208.mdb

Migration Toolkit invents the silly schema name 220208 for this database, and refuses to allow me to change it. I do not want to have a database called 220208 on my MySQL server. I'd prefer not to have to rename the source files before migrating them. 

How to repeat:
Create an Access database called "CAMFED Data 3 Ghana 220208.mdb"

Try to migrate it to MySQL.

Suggested fix:
Allow the user to change the name of the database/schema that will be created by the Migration Toolkit.
[17 Jun 2008 17:19] MySQL Verification Team
Thank you for the bug report. Could you please provide a smaple mdb file attaching  here with Files tab. Thanks in advance.
[18 Jun 2008 9:19] Chris Wilson
Database with an unusual "schema" name

Attachment: Database Name is not Schema.mdb (application/msaccess, text), 96.00 KiB.

[20 Jun 2008 10:50] Chris Wilson
Change back to Open status?
[20 Jun 2008 15:09] MySQL Verification Team
Thank you for the feedback.
[5 Jun 2009 21:05] Q Kan
Recently, I tried to migrate a MS SQL database to MySQL, using MySQL Migration Toolkit 1.1.17, I found that the default target schema name is the original name plus "_dbo".  I cannot change the target schema name in the Migration Toolkit.

A workaround is, instead of having the Migration Toolkit generating the target schema and tables automatically, use it to generate a schema and tables creation script.  Modify the script and run it in Query Browser.
[19 Oct 2009 11:26] Susanne Ebrecht
The workaround here is the SQL command RENAME SCHEMA:

RENAME {DATABASE | SCHEMA} db_name TO new_db_name;


We are on the way to implement full functionality of MySQL Migration Tool into MySQL Workbench. We won't add this feature request anymore.

More informations about MySQL Workbench you will find here:

[12 Mar 2010 18:21] Keith Macdonald
When will the Migration Toolkit functionality be in the Workbench?
Hopefully, when it is there, it will not have this bug in it (i.e. not being able to choose the target schema name)
[29 Aug 2011 4:02] inew inew
I got to reply this post since it takes me so much time to find the answer.
The answer is, the mysql migration toolkit supports you change schema name. 
I got this from 
which says
"Simply select the target table name in the list and press F2 or slow click the name 2 times as common in Windows. Then enter the new name for the table."

That is it. 
I do not count on the mirgratioin function of WB considering Oracle is Oracle's focal business.