Bug #12413 Ability to specify different target database name
Submitted: 6 Aug 2005 10:55 Modified: 6 Aug 2005 12:33
Reporter: Paul Birkel Email Updates:
Status: Closed Impact on me:
Category:MySQL Migration Toolkit Severity:S3 (Non-critical)
Version:1.0.12 rc OS:Microsoft Windows (WinXP)
Assigned to: CPU Architecture:Any

[6 Aug 2005 10:55] Paul Birkel
It would be valuable if one could override the assumption that the target/migrated database had the same name as the source/migrating database.   There is currently no mechanism to specify these separately even though the user does specify all of the other target database/connection/host information. 

How to repeat:
Not applicable

Suggested fix:
This could be added to the "Target Database" GUI page -- although it is worthwhile to note that what is currently specified there is only the target DBMS and *not* a database.  This capability would be very valuable in my environment where naming conventions differ between my source and target DBMS environments.  Thanks for your consideration (and great job -- rc12 continues to scratch ever more of my itches :-).
[6 Aug 2005 12:33] Michael G. Zinner
Thank you for your bug report. This issue has already been fixed
in the latest released version of that product, which you can download at 

Additional info:

You can rename every object (schema, table, columns, indices) on the Advanced Mapping page.  To get to that page you have to press [Advanced >>] button on the Object Mapping page and enable the option 

[X] Enable detailed mapping definitions in next step

Another, simplier way is to change the object names on the manual editing page. 

Simply select the filter [Show All Objects] there, click on the schema or table you want to rename in the Target Objects column and press F2.

After you have renamed an object, all SQL Create statements will be re-generated. You can check this by displaying the SQL statements with the [Advanced >>] button. 

If you want to modify the SQL statements manually please do this after you have renamed the objects, or you manual changes will be lost due to the re-generation of the SQL statements.

I will make a forum posting about this as it may benefit more users.