Exporting Azure SQL Database to bacpac failure

Hi Sheenam Yadav

Greeting!

As I understand that, you are facing an issue in Exporting Azure SQL Database to bacpac file.

there are some considerations here.

• 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 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.
• 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 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.
• For larger databases, BACPAC export/import might take a long time, and might fail for various reasons. there are some Limitation:
  • xporting a BACPAC file to Azure premium storage using the methods discussed in this article isn't supported.
  • Storage behind a firewall is currently not supported.
  • Immutable storage is currently not supported.
  • Azure SQL Managed Instance 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.
  • 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.
  Please refer the Microsoft official Documentation this may helpful more details. https://learn.microsoft.com/en-us/azure/azure-sql/database/database-export?view=azuresql Hope this helps. Do let us know if you any further queries. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Hi Sheenam Yadav

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Hi Sheenam Yadav

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.