Skip to content

Commit 211233e

Browse files
committed
adding vm tips
1 parent 0f27ebc commit 211233e

1 file changed

Lines changed: 12 additions & 0 deletions

File tree

docs/tools/sqlpackage/troubleshooting-import-export-sqlpackage.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,18 @@ As an alternative operation to obtain the database schema and data while skippin
5353

5454
In scenarios where the OS disk space is limited and runs out during the export, the use of `/p:TempDirectoryForTableData` allows the data for export to be buffered on an alternative disk. The space required for this action may be large and is relative to the full size of the database. That and other properties are available to tune the [SqlPackage.exe Export](sqlpackage-export.md) operation.
5555

56+
## Azure SQL Database
57+
58+
The following tips are specific to running import or export against Azure SQL Database from an Azure virtual machine (VM):
59+
60+
- use Business Critical or Premium tier database for best performance
61+
- use SSD storage on the VM and ensure there is enough room to unzip the bacpac
62+
- execute SqlPackage from a VM in the same region as the database
63+
- enable accelerated networking in the VM
64+
65+
For more information on utilizing a PowerShell script to collect more information about an import operation, please see a [TechCommunity blog post](https://techcommunity.microsoft.com/t5/azure-database-support-blog/lesson-learned-211-monitoring-sqlpackage-import-process/ba-p/3556382) on the topic.
66+
67+
5668
## Next steps
5769

5870
- Learn more about [SqlPackage Import](sqlpackage-import.md)

0 commit comments

Comments
 (0)