问题描述
在MySQL工作台上使用内置的迁移工具时遇到问题.
I am having an issue using the built in migration tool on MySQL workbench.
我正在将一个很大的数据库从MS SQL 2014迁移到MySQL.
I am migrating a very large database from MS SQL 2014 to MySQL.
MS SQL服务器已本地部署在我的Windows 8.1桌面上，而MySQL服务器则在Ubuntu服务器之上的网络上运行.
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 am getting a series of the following errors on the final "bulk transfer" stage of the 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 schemata of the tables migrated over fine, the issue is limited to the transfer of the data itself.
如果您想查看任何特定变量以帮助诊断问题，请询问，我会及时提供.
If there are any particular variable you would like to see to help diagnose the problem, please just ask and I will provide them promptly.
在这方面的任何帮助都将是巨大的，所有在线消息来源都是破产的.
Any assistance on this would be great, all sources online were a bust.
我什至不确定是它的MS SQL还是MySQL抛出大小错误...
Im not even sure whether its MS SQL or MySQL throwing the size error...
推荐答案
自从一年多以前，您可能已经解决了此问题，但是也许其他人(例如我)也遇到了同样的问题，因此我想补充一下我的解决方案:
Since this one is over a year ago you might have solved this issue already, but maybe others (like me) have the same problem and so I want to add my solution:
在一个MySQL论坛中，我发现一个人发布了一个公式，并为我的服务器和系统计算了公式之后，发现我试图使用2 GB太多的RAM，而系统没有此RAM.就在这里，希望对您有所帮助.
In some MySQL forum I found a guy posted a formula and after calculating it for my server and my system I found out, that I tried to use 2 GB too much RAM which the system did not have. Here it is and I hope it helps someone.
RAM = innodb_pool_buffer_size + key_buffer_size +
( (read_buffer_size + sort_buffer_size + read_rnd_buffer_size + join_buffer_size)
* max_connection )
这篇关于迁移问题:MS SQL> MySQL:插入缓冲存储器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！