Migration problems: MS SQL> MySQL: insert buffer memory

Question

I am having a problem using the built-in migration tool to MySQL Workbench.

I am moving a very large database from MS SQL 2014 to MySQL.

The MS SQL server is deployed locally on my (Windows 8.1) desktop, and the MySQL server runs on my network on top of Ubuntu Server.

I get a series of the following errors at the final stage of the "mass transfer" of migration.

`VHR_AGE`.`FlxTable`:Copying 33 columns of 311 rows from table [VHR_AGE].[dbo].[FlxTable]
ERROR: `VHR_AGE`.`FlxTable`:Not enough memory to allocate insert buffer of size 1073741824
`VHR_AGE`.`FlxTable`:Finished copying 0 rows in 0m00s

The schemes of the tables carried over under the penalty, the problem is limited to the transfer of the data itself.

If there is any particular variable that you would like to see to help diagnose the problem, just ask and I provided them immediately.

Any help on this would be great, all sources on the Internet were a bust.

: , MS SQL MySQL ...

Answer 1

, , , , ( ) ​​ , :

- MySQL , , , 2 , . , , -.

RAM = innodb_pool_buffer_size + key_buffer_size + 
   ( (read_buffer_size + sort_buffer_size + read_rnd_buffer_size + join_buffer_size)
         * max_connection )

Answer 2

MySQL. bulk_insert_buffer_size MySQL.

Answer 3

, MYSQL. , 1 , ( , bulk_insert_buffer_size). :

• , .
• (.. - MS SQL).
• ( )

Answer 4

, this. " MYSQL" . .

Answer 5

Talend. , . ..

MSSQL, MySQL, . MySQL MSSQL. , WYSIWYG. Eclipse, , , .

Answer 6

, , . . , . - , mysql .

: 1073741824

If you just reduce the size of the buffer, it will work for you. You should try to reduce it to ~ 64.