Bug #69961 During migration
Submitted: 8 Aug 2013 11:05 Modified: 19 Sep 2013 20:21
Reporter: sudhir Tripathi Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Migration Severity:S1 (Critical)
Version:5.2.47 CE OS:Windows (Windows 7)
Assigned to: CPU Architecture:Any

[8 Aug 2013 11:05] sudhir Tripathi
Description:
Step -1 Start Migration wizard 
Step -2 Select Data source Microsoft SQl Server 2008 R2 
Step- 3 Select ODBC (Native )
Step- 4 Give user name and Password test connection, its ok
Step- 5 Move To next select destination as MySql 5.2 give user Id password and             test Connection ,Its ok.
Step- 6 in the last stage of Migration it display Finalizing foreign key migration...hear it take some time then display message 

- Migration finished

Migrate Selected Objects finished

Generate SQL CREATE Statements....

- Generating SQL...

Generate SQL CREATE Statements finished

Finished performing tasks.

Step - & on Clikc next 

it will show Work bench Not response ding in Top of bar  

How to repeat:
in same way i found thes issue several time
[8 Aug 2013 11:45] MySQL Verification Team
Please check for duplicate: http://bugs.mysql.com/bug.php?id=67129 . Thanks.
[8 Aug 2013 13:33] sudhir Tripathi
no this bug http://bugs.mysql.com/bug.php?id=67129 . is different from my case
[12 Aug 2013 16:07] Sergio Andres De La Cruz Rodriguez
Hi Sudhir:

Thanks for your report. The last page of the Migration Wizard might take a while to create the final report. I just want you to confirm if this is the case (i.e. that it takes a while to render the final page). It can take several minutes if the database structure/data is long enough.

Can you confirm this, please?
[13 Aug 2013 11:49] sudhir Tripathi
No I am face this from when Migration state finish move to next step
and for time prospective i am waiting more than 5 to 6 hr.
[19 Aug 2013 20:21] MySQL Verification Team
Please try version 6.0.6. Thanks.
[20 Sep 2013 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".