Home Dashboard Directory Help
Search

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


Status: 

Active


14
0
Sign in
to vote
Type: Bug
ID: 807898
Opened: 11/6/2013 11:26:50 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

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.
Details
Sign in to post a comment.
Sign in to post a workaround.