So far not possible to import a 20G bacpac database into Azure SQL instance - by nicolas.tremblay

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 807898 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 11/6/2013 11:26:50 AM
Access Restriction Public


Tried all most common workflows to import a 20 Gigabytes Bacpac into Azure SQL, (Business 150Gig profile) and all failed.
Our biggest table which we think is the culprit, has 16.5 million rows, about 3GB (data&index) on-premise without compression.
As it fails when rebuilding an index, non-clustered On Azure, but the exact same process is working fine On-Premise.

Unless provided by other alternative, or better workflow, I now qualify this issue as a Showstopper.
Sign in to post a comment.