MySQL Bugs: #36127: Migrat Table data from Source MySQL database to same Destination MySQL Database

Bug #36127	Migrat Table data from Source MySQL database to same Destination MySQL Database
Submitted:	16 Apr 2008 10:24	Modified:	24 Mar 2009 13:52
Reporter:	Akash Kava	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	migration, Same, server, table

Description:
I ran into a problem, when I wanted to transfer 2 Million rows of one table to same server's different database. I tried using php mysql admin, it started and it hung upon mid way and didnt finish. I tried using MySQL Migration Toolkit, it has no way of selecting different table name and migration procedure on its way deleted the source table and all rows were deleted.

I think there must be a facility to change "Destination" table name and do the migration.

How to repeat:
1. Select Source Server as localhost MySQL
2. Select Destination Server as localhost MySQL
3. Select source database, and select one table to migrat
4. There is no way to select anything on target destination database... !!!!
5. It gives some sort of warning and by proceeding, it deletes Source Database's Source Table...

Suggested fix:
There must be a facility to choose Destination Database on Destination Server, so that we can do huge data migration from one database to another database on same server in order to do some maintanence. It is also useful to take backup.

I have temporiarily installed MSSQL server on same server to do migration, that is pretty awful step to do huge data migration.

You can easily find a client that has functionalities like 'duplicate table', 'copy table to other database' etc. with a single mouse-click.  Running such task through a JDBC or ODBC based migration tool is unnecessarily complicating things, I think.

(this is only a comment from another user to help you out. MySQL people will need to consider if there is a bug in the MySQL Migration Tool)

Please note, I am talking about transfering 2 to 4 million records, all other single click tools fail, they start migration and hung on it forever. Best part of Migration Toolkit is that it has the progress bar of transfering records. And it does not timeout.

However, we wrote the manual application in .NET to do it now, but still a small feature of selecting Target Database on Target Server, will make life easier.

Thank you for the bug report.

Many thanks for writing a bug report. MySQL Migration Toolkit is not for upgrading from older MySQL versions to actual version. Please use mysql_upgrade here.

I should add that duplication of a table is as easy as 

CREATE TABLE ... LIKE

and 

INSERT INTO target.... FROM SELECT * FROM source ...

No need to use a migration tool for that.