Merge pull request #36480 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-27 18:30 UTC

Author: learn-build-service-prod[bot]

azure-sql/database/database-export.md

@@ -1,11 +1,11 @@
 ---
 title: Export a Database to a BACPAC File
 titleSuffix: Azure SQL Database & Azure SQL Managed Instance
-description: Export a database to a BACPAC file using the Azure portal, PowerShell, Azure Data Studio, or SQL Server Management Studio.
+description: Export a database to a BACPAC file using the Azure portal, PowerShell, Visual Studio Code, or SQL Server Management Studio.
 author: WilliamDAssafMSFT
 ms.author: wiassaf
-ms.reviewer: mathoma, hudequei
-ms.date: 08/07/2025
+ms.reviewer: mathoma, hudequei, randolphwest
+ms.date: 01/26/2026
 ms.service: azure-sql
 ms.subservice: data-movement
 ms.topic: how-to
@@ -22,37 +22,44 @@ When you need to export a database for archiving or for moving to another platfo
 
 ## Considerations
 
-- For an export to be transactionally consistent, you must ensure either that no write activity is occurring during the export, or that you're exporting from a [transactionally consistent copy](database-copy.md) of your database.
-- If you're exporting to blob storage, the maximum size of a BACPAC file is 200 GB. To archive a larger BACPAC file, export to local storage with SqlPackage.
-- [Import and Export using Private Link](database-import-export-private-link.md) is in preview.
-- The Azure Storage file name can't end with `.` and can't contain special characters like a space character or `<`, `>`, `*`, `%`, `&`, `:`, `\`, `/`, `?`. The file name should be fewer than 128 characters long.
-- If the export operation exceeds 20 hours, it might be canceled. To increase performance during export, you can:
+For an export to be transactionally consistent, you must ensure either that no write activity is occurring during the export, or that you're exporting from a [transactionally consistent copy](database-copy.md) of your database.
 
-    - Temporarily increase your compute size.
-    - Cease all read and write activity during the export.
-    - Use a [clustered index](/sql/relational-databases/indexes/clustered-and-nonclustered-indexes-described) with non-null values on all large tables. Without clustered indexes, an export might fail if it takes longer than 6-12 hours. This is because the export service needs to complete a table scan to try to export entire table. A good way to determine if your tables are optimized for export is to run `DBCC SHOW_STATISTICS` and make sure that the *RANGE_HI_KEY* isn't null and its value has good distribution. For details, see [DBCC SHOW_STATISTICS](/sql/t-sql/database-console-commands/dbcc-show-statistics-transact-sql).
-    - For larger databases, BACPAC export/import might take a long time, and might fail for various reasons.
-    
-> [!NOTE]
-> BACPACs are not intended to be used for backup and restore operations. Azure automatically creates backups for every user database. For details, see [business continuity overview](business-continuity-high-availability-disaster-recover-hadr-overview.md) and [Automated backups in Azure SQL Database](automated-backups-overview.md?view=azuresql-db&preserve-view=true) or [Automated backups in Azure SQL Managed Instance](../managed-instance/automated-backups-overview.md?view=azuresql-mi&preserve-view=true).
+If you're exporting to blob storage, the maximum size of a BACPAC file is 200 GB. To archive a larger BACPAC file, export to local storage with SqlPackage.
+
+[Import or export an Azure SQL Database by using private link](database-import-export-private-link.md) is in preview.
+
+The Azure Storage file name can't end with `.` and can't contain special characters like a space character or `<`, `>`, `*`, `%`, `&`, `:`, `\`, `/`, `?`. The file name should be fewer than 128 characters long.
+
+If the export operation exceeds 20 hours, it might be canceled. To increase performance during export, you can:
+
+- Temporarily increase your compute size.
+
+- Cease all read and write activity during the export.
+
+- Use a [clustered index](/sql/relational-databases/indexes/clustered-and-nonclustered-indexes-described) with non-null values on all large tables. Without clustered indexes, an export might fail if it takes longer than 6-12 hours. This is because the export service needs to complete a table scan to try to export entire table. A good way to determine if your tables are optimized for export is to run `DBCC SHOW_STATISTICS` and make sure that the `RANGE_HI_KEY` isn't null and its value has good distribution. For details, see [DBCC SHOW_STATISTICS (Transact-SQL)](/sql/t-sql/database-console-commands/dbcc-show-statistics-transact-sql).
+
+- For larger databases, BACPAC export/import might take a long time, and might fail for various reasons.
+
+> [!NOTE]  
+> BACPACs aren't intended to be used for backup and restore operations. Azure automatically creates backups for every user database. For details, see [business continuity overview](business-continuity-high-availability-disaster-recover-hadr-overview.md) and [Automated backups in Azure SQL Database](automated-backups-overview.md?view=azuresql-db&preserve-view=true) or [Automated backups in Azure SQL Managed Instance](../managed-instance/automated-backups-overview.md?view=azuresql-mi&preserve-view=true).
 
 <a id="the-azure-portal"></a>
 
 ## Export from the Azure portal
 
-- You can use the Azure portal to export a BACPAC of a database in an [Azure SQL Database logical server](logical-servers.md). 
+- You can use the Azure portal to export a BACPAC of a database in an [Azure SQL Database logical server](logical-servers.md).
 - Using the Azure portal isn't currently supported to export a BACPAC of a database from [Azure SQL Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md).
 
-> [!NOTE]
+> [!NOTE]  
 > Machines processing import/export requests submitted through the Azure portal or PowerShell need to store the BACPAC file and temporary files generated by the Data-Tier Application Framework (DacFX). The disk space required varies significantly among databases with the same size and can require disk space up to three times the size of the database. Machines running the import/export request only have 450GB local disk space. As a result, some requests might fail with the error `There is not enough space on the disk`. In this case, the workaround is to run SqlPackage on a machine with enough local disk space. Use the [SQLPackage utility](#sqlpackage-utility) to import/export databases larger than 150GB to avoid this issue.
 
 1. To export a database using the [Azure portal](https://portal.azure.com), open the page for your database and select **Export** on the toolbar.
 
-    :::image type="content" source="media/database-export/sql-database-export-menu-button.png" alt-text="Screenshot that highlights the Export button." lightbox="media/database-export/sql-database-export-menu-button.png":::
+   :::image type="content" source="media/database-export/sql-database-export-menu-button.png" alt-text="Screenshot that highlights the Export button." lightbox="media/database-export/sql-database-export-menu-button.png":::
 
 1. Specify the BACPAC filename, select an existing Azure storage account and container for the export, and then provide the appropriate credentials for access to the source database. A SQL **Server admin login** is needed here even if you're the Azure admin, as being an Azure admin doesn't equate to having admin permissions in Azure SQL Database or Azure SQL Managed Instance.
 
-    :::image type="content" source="media/database-export/sql-database-export-database.png" alt-text="Screenshot shows the Export Database page with username and password specified.":::
+   :::image type="content" source="media/database-export/sql-database-export-database.png" alt-text="Screenshot shows the Export Database page with username and password specified.":::
 
 1. Select **OK**.
 
@@ -67,12 +74,12 @@ To export a database in SQL Database using the [SQLPackage](/sql/tools/sqlpackag
 This example shows how to export a database using SqlPackage with Active Directory Universal Authentication:
 
 ```cmd
-SqlPackage /a:Export /tf:testExport.BACPAC /scs:"Data Source=apptestserver.database.windows.net;Initial Catalog=MyDB;" /ua:True /tid:"apptest.onmicrosoft.com"
+SqlPackage /a:Export /tf:testExport.bacpac /scs:"Data Source=apptestserver.database.windows.net;Initial Catalog=MyDB;" /ua:True /tid:"apptest.onmicrosoft.com"
 ```
 
-## Azure Data Studio
+## Visual Studio Code
 
-[Azure Data Studio](/azure-data-studio) is a free, open-source tool and is available for Windows, Mac, and Linux. The "SQL Server dacpac" extension provides a wizard interface to SqlPackage operations including export and import. For more information on installing and using the extension, see [SQL Server dacpac extension](/azure-data-studio/extensions/sql-server-dacpac-extension).
+The MSSQL extension for Visual Studio Code is a free, open-source extension available for Windows, macOS, and Linux. The extension includes the [Data-tier Application (Preview)](/sql/tools/visual-studio-code-extensions/mssql/mssql-data-tier-application) experience for SqlPackage operations, including export and import. For more information on installing and using the extension, see the [MSSQL extension for Visual Studio Code](/sql/tools/visual-studio-code-extensions/mssql/mssql-extension-visual-studio-code).
 
 ## SQL Server Management Studio (SSMS)
 
@@ -113,9 +120,10 @@ Use the [Database Operations - Cancel](/rest/api/sql/database-operations/cancel)
 Stop-AzSqlDatabaseActivity -ResourceGroupName $ResourceGroupName -ServerName $ServerName -DatabaseName $DatabaseName -OperationId $Operation.OperationId
 ```
 
-> [!NOTE]
+> [!NOTE]  
 > To cancel export operation, you need to have one of the following roles:
-> - The [SQL DB Contributor](/azure/role-based-access-control/built-in-roles#sql-db-contributor) role or 
+>
+> - The [SQL DB Contributor](/azure/role-based-access-control/built-in-roles#sql-db-contributor) role or
 > - A [custom Azure RBAC role](/azure/role-based-access-control/custom-roles) with `Microsoft.Sql/servers/databases/operations` permission
 
 ## Limitations
@@ -124,14 +132,15 @@ Stop-AzSqlDatabaseActivity -ResourceGroupName $ResourceGroupName -ServerName $Se
 - Storage behind a firewall is currently not supported.
 - Immutable storage is currently not supported.
 - [Azure SQL Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md) doesn't currently support exporting a database to a BACPAC file using the Azure portal or Azure PowerShell. To export a managed instance into a BACPAC file, use SQL Server Management Studio (SSMS) or [SQLPackage](/sql/tools/sqlpackage).
-- Currently, the Import/Export service does not support Microsoft Entra ID authentication when MFA is required.
-- Import\Export services only support SQL authentication and Microsoft Entra ID. Import\Export is not compatible with Microsoft Identity application registration.
+- Currently, the Import/Export service doesn't support Microsoft Entra ID authentication when MFA is required.
+- Import\Export services only support SQL authentication and Microsoft Entra ID. Import\Export isn't compatible with Microsoft Identity application registration.
 
 ## Related content
 
-- To learn about long-term backup retention of a single database and pooled databases as an alternative to exporting a database for archive purposes, see [Long-term backup retention](long-term-retention-overview.md). You can use SQL Agent jobs to schedule [copy-only database backups](/sql/relational-databases/backup-restore/copy-only-backups-sql-server) as an alternative to long-term backup retention.
-- To learn about importing a BACPAC to a SQL Server database, see [Import a BACPAC to a SQL Server database](/sql/relational-databases/data-tier-applications/import-a-BACPAC-file-to-create-a-new-user-database).
-- To learn about exporting a BACPAC from a SQL Server database, see [Export a Data-tier Application](/sql/relational-databases/data-tier-applications/export-a-data-tier-application)
-- To learn about using the Data Migration Service to migrate a database, see [Migrate from SQL Server to Azure SQL Database offline using DMS](/azure/dms/tutorial-sql-server-to-azure-sql).
-- If you're exporting from SQL Server as a prelude to migration to Azure SQL Database, see [Migrate a SQL Server database to Azure SQL Database](migrate-to-database-from-sql-server.md).
-- To learn how to manage and share storage keys and shared access signatures securely, see [Security recommendations for Blob storage](/azure/storage/blobs/security-recommendations).
+- [Long-term retention backups - Azure SQL Database and Azure SQL Managed Instance](long-term-retention-overview.md)
+- [copy-only database backups](/sql/relational-databases/backup-restore/copy-only-backups-sql-server)
+- [Import a BACPAC to a SQL Server database](/sql/relational-databases/data-tier-applications/import-a-BACPAC-file-to-create-a-new-user-database)
+- [Export a Data-tier Application](/sql/relational-databases/data-tier-applications/export-a-data-tier-application)
+- [Migrate from SQL Server to Azure SQL Database offline using DMS](/azure/dms/tutorial-sql-server-to-azure-sql)
+- [Migrate a SQL Server database to Azure SQL Database](migrate-to-database-from-sql-server.md)
+- [Security recommendations for Blob storage](/azure/storage/blobs/security-recommendations)

azure-sql/database/database-import-export-hang.md

@@ -4,19 +4,19 @@ titleSuffix: Azure SQL Database & Azure SQL Managed Instance
 description: Azure SQL Database and Azure SQL Managed Instance Import/Export service takes a long time to import or export a database
 author: WilliamDAssafMSFT
 ms.author: wiassaf
-ms.reviewer: mathoma, hudequei, sureshka
-ms.date: 06/13/2025
+ms.reviewer: mathoma, hudequei, sureshka, randolphwest
+ms.date: 01/26/2026
 ms.service: azure-sql
 ms.subservice: data-movement
 ms.topic: troubleshooting
 ms.custom:
   - sqldbrb=1
-monikerRange: "=azuresql || =azuresql-db || =azuresql-mi "
+monikerRange: "=azuresql || =azuresql-db || =azuresql-mi"
 ---
 
 # Azure SQL Database and SQL Managed Instance Import/Export service takes a long time to import or export a database
 
-[!INCLUDE[appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
+[!INCLUDE [appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
 
 When you use the Import/Export service, the process might take longer than expected. This article describes the potential causes for this delay and alternative workaround methods.
 
@@ -32,26 +32,26 @@ The Azure SQL Database Import/Export service provides a limited number of comput
 
 Additionally, as the Import/Export service performs a logical backup of the database the time to complete is more dependent on the number of objects in the database than a traditional physical database backup.
 
-> [!NOTE]
+> [!NOTE]  
 > After resources are assigned and a request starts to process, the service automatically cancels the request after two days.
 
 ## Recommended solutions
 
 If your database exports are used only for recovery from accidental data deletion, all the Azure SQL Database editions provide self-service restoration capability from system-generated backups. But if you need these exports for other reasons, and if you require consistently faster or more predictable import/export performance, consider the following options:
 
-- [Export to a BACPAC file by using the SQLPackage utility](./database-export.md#sqlpackage-utility).
-- [Export to a BACPAC file by using Azure Data Studio](./database-export.md#azure-data-studio).
-- [Export to a BACPAC file by using SQL Server Management Studio (SSMS)](./database-export.md#sql-server-management-studio-ssms).
+- [Export to a BACPAC file by using the SQLPackage utility](database-export.md#sqlpackage-utility).
+- [Export to a BACPAC file by using Visual Studio Code](/sql/tools/visual-studio-code-extensions/mssql/mssql-data-tier-application).
+- [Export to a BACPAC file by using SQL Server Management Studio (SSMS)](database-export.md#sql-server-management-studio-ssms).
 - Run the BACPAC import or export directly in your code by using the Microsoft SQL Server Data-Tier Application Framework (DacFx) API. For additional information, see:
-  * [Export a data-tier application](/sql/relational-databases/data-tier-applications/export-a-data-tier-application)
-  * [Microsoft.SqlServer.Dac Namespace](/dotnet/api/microsoft.sqlserver.dac)
+  - [Export a data-tier application](/sql/relational-databases/data-tier-applications/export-a-data-tier-application)
+  - [Microsoft.SqlServer.Dac Namespace](/dotnet/api/microsoft.sqlserver.dac)
 
 ## Things to consider when you export or import a database
 
-- All the methods discussed in this article consume Database Transaction Units (DTUs) or CPU quota, which causes throttling by the Azure SQL Database service. You can [view the DTU stats for the database on the Azure portal](./monitor-tune-overview.md#azure-sql-database-and-azure-sql-managed-instance-resource-monitoring). If the database has reached its resource limits, [upgrade the service tier](scale-resources.md) to add more resources.
+- All the methods discussed in this article consume Database Transaction Units (DTUs) or CPU quota, which causes throttling by the Azure SQL Database service. You can [view the DTU stats for the database on the Azure portal](monitor-tune-overview.md#azure-sql-database-and-azure-sql-managed-instance-resource-monitoring). If the database has reached its resource limits, [upgrade the service tier](scale-resources.md) to add more resources.
 - Ideally, you should run client applications (like the sqlpackage utility or your custom DAC application) from a VM in the same region as your database. Otherwise, you might experience performance issues related to network latency.
 - Exporting large tables without clustered indexes can be very slow or even cause failure. This behavior occurs because the table can't be split up and exported in parallel. Instead, it must be exported in a single transaction, and that causes slow performance and potential failure during export, especially for large tables.
 
 ## Related documents
 
-[Considerations when exporting a database](./database-export.md#considerations)
+[Considerations when exporting a database](database-export.md#considerations)