Bug #67640 Memory Error on Migrating SQL Server db to MySQL
Submitted: 19 Nov 2012 20:13 Modified: 12 Jun 2013 6:21
Reporter: Kevin Penrose Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Migration Severity:S2 (Serious)
Version:5.2.44 OS:Linux (Linux 3.2.0-33-generic)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[19 Nov 2012 20:13] Kevin Penrose
Description:
Database connections are successful, using FreeTDS for the SQL server connection.  Schema import gets about halfway through and 
and error is reported.  MemoryError - I have included the log file.  Let me know if you need more informtion.

----- Developer Notes -----

MySQL Workbench CE for Linux/Unix version 5.2.44  revision 9933
Configuration Directory: /home/kpenrose/.mysql/workbench
Data Directory: /usr/share/mysql-workbench
Cairo Version: 1.10.2
OS: Linux 3.2.0-33-generic
CPU: 2x Intel(R) Pentium(R) Dual  CPU  E2140  @ 1.60GHz 1600.161 MHz, 2.0 GB RAM
Distribution: Ubuntu 12.04.1 LTS

How to repeat:
Nothing special.  Connect to databases, select a complete schema import, and the failure occurs.
Running on an x86_64 12.04 Ubuntu install.
[26 Nov 2012 16:24] MySQL Verification Team
Thank you for the bug report. Please specify the source and destination server versions. Thanks.
[26 Nov 2012 16:38] Kevin Penrose
Source db is MS SqlServer 2008.  Database product version reports as 10.00.2531.
Destination db is MySql 5.5.
Using FreeTDS to connect to the SqlServer.
[21 Mar 2013 17:41] Armando Lopez Valencia
Hello.
Can you please try with the latest WB version (5.2.47) and let us know if you can still reproduce this problem?
Thanks.
[21 Mar 2013 18:10] Kevin Penrose
I have upgraded to the 5.2.47 version, and the error persists.
[21 Mar 2013 18:11] Kevin Penrose
This is the error log after updating to version 5.2.47.

Attachment: error.log (application/octet-stream, text), 7.98 KiB.

[22 Mar 2013 18:46] Armando Lopez Valencia
Thanks a lot for your report.
[12 Jun 2013 6:21] Philip Olson
Fixed as of the upcoming MySQL Workbench 6.0.x release, and here's the changelog entry:

Executing a complete schema import during a migration could run out of
memory if the schema contained a lot of views, procedures, and function
definitions. The memory handling was improved.

Thank you for the bug report.