You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sql-database/import-export-from-vm.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,15 +61,7 @@ The following steps show you how to connect to your virtual machine using a remo
61
61
62
62
8. You might receive a certificate warning during the sign-in process. Choose **Yes** or **Continue** to proceed with the connection.
63
63
64
-
## Store the imported or exported .BACPAC
65
64
66
-
Because SqlPackage operates with the filesystem, you can use the storage feature that best suits your needs for both performance (the speed of import or export operations), and cost. Importing and exporting databases uses [.BACPAC files](https://docs.microsoft.com/sql/relational-databases/data-tier-applications/data-tier-applications#bacpac) stored in Azure Storage.
67
-
68
-
The .BACPAC file can be stored in [Azure Blobs](https://docs.microsoft.com/azure/storage/blobs/storage-blobs-overview), or [Azure Files](https://docs.microsoft.com/azure/storage/files/storage-files-introduction). Whether to use Azure Blobs or Azure Files depends on your specific business requirements. Azure Blobs will cost less than a premium Azure file share, but will take a longer time for the import or export operation to complete.
69
-
70
-
To upload or download .BACPAC files, see [Transfer data with AzCopy and Blob storage](../storage/common/storage-use-azcopy-blobs.md), and [Transfer data with AzCopy and file storage](../storage/common/storage-use-azcopy-files.md).
71
-
72
-
Depending on your environment, you might need to [Configure Azure Storage firewalls and virtual networks](../storage/common/storage-network-security.md).
73
65
74
66
## Install SqlPackage
75
67
@@ -158,7 +150,15 @@ Even with all of the above conditions, the import export service may not meet th
158
150
3. VM should have SSD with adequate size for generating temp artifacts before uploading to blob storage.
159
151
4. VM should have adequate core and memory configuration for the specific database.
160
152
153
+
## Store the imported or exported .BACPAC file
161
154
155
+
Because SqlPackage operates with the filesystem, you can use the storage feature that best suits your needs for both performance (the speed of import or export operations), and cost. Importing and exporting databases uses [.BACPAC files](https://docs.microsoft.com/sql/relational-databases/data-tier-applications/data-tier-applications#bacpac) stored in Azure Storage.
156
+
157
+
The .BACPAC file can be stored in [Azure Blobs](https://docs.microsoft.com/azure/storage/blobs/storage-blobs-overview), or [Azure Files](https://docs.microsoft.com/azure/storage/files/storage-files-introduction). Whether to use Azure Blobs or Azure Files depends on your specific business requirements. Azure Blobs will cost less than a premium Azure file share, but will take a longer time for the import or export operation to complete.
158
+
159
+
To upload or download .BACPAC files, see [Transfer data with AzCopy and Blob storage](../storage/common/storage-use-azcopy-blobs.md), and [Transfer data with AzCopy and file storage](../storage/common/storage-use-azcopy-files.md).
160
+
161
+
Depending on your environment, you might need to [Configure Azure Storage firewalls and virtual networks](../storage/common/storage-network-security.md).
0 commit comments