I suggest you ...

Azure Sql Import Bacpac slow

We are testing a production database migration to Azure SQL. The database is 50GB and even on the S3 tier we are going on 30 hours still and the import isn't complete (pegged at 100% DTU). At this point I couldn't even tell you when this will finish. I understand I could have chosen the highest premium tier to import this and it might have been quicker, however I only want to test this database and right now I've lost 3-4 days on this (importing at S0, S1 tiers). My suggestion is to allow an option when going through the import process that imports the database at the highest tier and automatically downgrades it to the selected tier when it is finished. It is consumption based we get it, but an import shouldn't be this painful taking days isn't a good experience.

39 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Sam Bosell shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

3 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base