SQL Azure导入缓慢，挂起，但本地导入需要3分钟

I have a not-that-large database that I'm trying to migrate to SQL Azure, about 1.6 gigs. I have the BACPAC file in blob storage, start the import, and then... nothing. It gets to 5% as far as the status goes, but otherwise goes nowhere fast. After 10 hours, the database size appears to be 380 MB, and the monitoring shows on average around 53 successful connections per hour, with no failures. It appears to still be going.

我有一个非常大的数据库,我正在尝试迁移到SQL Azure,大约1.6演出。我在blob存储中有BACPAC文件,开始导入,然后......没有。就状态而言,它达到了5%,否则无处可去。 10个小时后,数据库大小似乎为380 MB,监控平均每小时显示大约53个成功连接,没有失败。它似乎还在继续。

I took the same BACPAC to my local machine at home, and I can import the same database in just under three minutes, so I'm making the assumption that the integrity of the file is all good.

我把相同的BACPAC带到了家里的本地机器上,我可以在不到三分钟的时间内导入同一个数据库,所以我假设文件的完整性都很好。

What could possibly be the issue here? I can't just keep the app I'm migrating offline for days while this goes on. There must be something fundamentally different that it's choking on.

这可能是什么问题?我不能只是保持应用程序我正在离线数天,而这一直在继续。必须有一些根本不同的东西,它正在窒息。

1 个解决方案

#1

Ugh, I hate answering my own question, but I figured out what the issue is. It appears to have to do with their new basic-standard-premium tiers (announced April 2014). The database imports to the old web-business levels no problem. Because the new tiers are built around throttling for "predictable performance," they make the high volume transactions of importing crazy slow.

呃,我讨厌回答我自己的问题,但我弄清楚问题是什么。它似乎与他们新的基本标准高级等级(2014年4月宣布)有关。数据库导入到旧的Web业务级别没问题。由于新层是围绕“可预测的性能”进行限制而构建的,因此它们使导入疯狂的大量交易变得缓慢。