SOLVED

SQL Migration - SQLPackage.exe takes so much time to export databases

%3CLINGO-SUB%20id%3D%22lingo-sub-826561%22%20slang%3D%22en-US%22%3ESQL%20Migration%20-%20SQLPackage.exe%20takes%20so%20much%20time%20to%20export%20databases%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-826561%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20in%20process%20of%20migrating%20from%20SQL%20server%202088%20R2%20to%20Azure%20SQL.%20We%20are%20going%20to%20migrate%20around%20144%20databases%2C%20size%20ranges%20from%2050%20GB%20-%20150%20GB%20per%20DB.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20using%20SQLPackage%20to%20export%20%26amp%3B%20import%20DBs%20into%20Azure%20SQL.%20For%20this%2C%20we%20are%20using%20a%20temp%20Azure%20VM%20to%20run%20this%20migration.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDuring%20our%20test%2C%20we%20noticed%20that%20exporting%20databases%20taking%20long%20time%2C%20around%20half%20an%20hour%20per%20DB.%20(I%20was%20using%26nbsp%3B%3CFONT%3EStandard%20L32s_v2%20(32%20vcpus%2C%20256%20GiB%20memory)%3C%2FFONT%3EVM%2C%20local%20NVM%20disks%20for%20data%2C%20log%20%26amp%3B%20temp%20to%20get%20higher%20throughput%20and%20IOPS).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20anyway%20that%20can%20speedup%20the%20export%20process%20(beside%20adding%20more%20VMs%20to%20run%20export%2Fimport%20in%20parallel)%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20know%20it%20is%20generic%20question%2C%20and%20each%20database%20is%20different%20from%20the%20other%20%3A)%2C%20but%20any%20help%20would%20be%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-826561%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20SQL%20DB%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-952457%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Migration%20-%20SQLPackage.exe%20takes%20so%20much%20time%20to%20export%20databases%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-952457%22%20slang%3D%22en-US%22%3EWe%20ended%20up%20with%20using%20Standard%20L32s_v2%20VM%20and%20running%20import%2Fexport%20process%20in%20parallel%20using%20different%20disks.%20(Disk%20for%20each%20component%3A%20data%2C%20log%2C%20export%2C%20import)%20and%20it%20was%20quick.%3C%2FLINGO-BODY%3E
Occasional Contributor

Hello,

 

We are in process of migrating from SQL server 2088 R2 to Azure SQL. We are going to migrate around 144 databases, size ranges from 50 GB - 150 GB per DB.

 

We are using SQLPackage to export & import DBs into Azure SQL. For this, we are using a temp Azure VM to run this migration.

 

During our test, we noticed that exporting databases taking long time, around half an hour per DB. (I was using Standard L32s_v2 (32 vcpus, 256 GiB memory) VM, local NVM disks for data, log & temp to get higher throughput and IOPS).

 

Is there anyway that can speedup the export process (beside adding more VMs to run export/import in parallel)?

 

I know it is generic question, and each database is different from the other :) , but any help would be appreciated.

1 Reply
best response confirmed by Mohamed Shehata (Occasional Contributor)
Solution
We ended up with using Standard L32s_v2 VM and running import/export process in parallel using different disks. (Disk for each component: data, log, export, import) and it was quick.