Bug #72231 Mysql workbench 6.0 insufficient memory during sql server database to mysql
Submitted: 4 Apr 2014 3:20 Modified: 4 Apr 2014 12:07
Reporter: Raja Ray Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Utilities Severity:S3 (Non-critical)
Version:6.0 OS:Windows
Assigned to: CPU Architecture:Any

[4 Apr 2014 3:20] Raja Ray
Description:
Migrate one huge volume sql server database (two tables with more than one crore rows and primary key, foreign key relationship) to mysql. After few hours of workbench is getting hanged, telling "Insufficient memory to continue the execution of the program". Also check with unique constraint more than 16 in one table.

How to repeat:
Migrate one huge volume sql server database (two tables with more than one crore rows and primary key, foreign key relationship) to mysql. Also check with unique constraint more than 16 in one table.
[4 Apr 2014 3:23] Raja Ray
Bug Snap

Attachment: MySQL_Workbench_Bug.png (image/png, text), 40.04 KiB.

[4 Apr 2014 8:05] Peter Laursen
You probably hit the memory allocation limit of a 32 bit application (2 GB as default - 3 GB with a registry hack) on 64 bit Windows.

I don't exclude that WB could organize its internal memory more efficient. But as long as the application is 32 bit it will not make a lot of difference I believe.

There is one problem with ODBC: it does not have a CHUNK mechanism (like the LIMIT clause in MySQL), so data cannot be fetched from the soruce in 'portions'.

Peter
(not a MySQL/Oracle person)
[4 Apr 2014 12:07] MySQL Verification Team
Thank you for the bug report. Duplicate of http://bugs.mysql.com/bug.php?id=67129 .