Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Azure sql database export to storage blob failed

I tried to export Sql Database in azure to storage blob but the operation failed. I do this task daily last month and this issue is new. It shows as follows :

Error encountered during the service operation.Blob https://blob link/dbname-2019-1-16-14-24.bacpac is not writeable. The remote server returned an error: (403) Forbidden.The remote server returned an error: (403) Forbidden.

like image 418
MOHAMED IDHRIS SHEIK DAWOOD Avatar asked Jan 16 '19 09:01

MOHAMED IDHRIS SHEIK DAWOOD


People also ask

Why can’t i export the Azure SQL database?

Based on case verbatim we understood you are trying to export the database with network restrictions in storage account. We checked the previous issues raised with similar error and found this is not supported and we need to enable all networks in storage account to be able to export the Azure SQL database.

Where is a BACPAC file stored in azure?

A BACPAC file can be stored in Azure Blob storage or in local storage in an on-premises location and later imported back into Azure SQL Database, Azure SQL Managed Instance, or a SQL Server instance.

How to export Azure SQL managed instance to BACPAC using PowerShell?

Azure SQL Managed Instance does not currently support exporting a database to a BACPAC file using Azure PowerShell. To export a managed instance into a BACPAC file, use SQL Server Management Studio or SQLPackage. Use the New-AzSqlDatabaseExport cmdlet to submit an export database request to the Azure SQL Database service.

How do I export a database in SQL Server management studio?

To export a database in SQL Database using the SqlPackage command-line utility, see Export parameters and properties. The SQLPackage utility ships with the latest versions of SQL Server Management Studio and SQL Server Data Tools for Visual Studio, or you can download the latest version of SqlPackage directly from the Microsoft download center.


1 Answers

I had the same problem. I have contacted Azure support and this is their response.

We recently identified a regression in the import/export service that is generating incorrect SAS tokens to the storage accounts.

The engineering team has rolled out the fix, but it might take some time for the fix to get applied worldwide.

Please try the following link to access Azure portal and then perform the export operations:

https://portal.azure.com/?feature.canmodifystamps=true&microsoft_azure_storage=stage1

The portal shows an orange title bar if you open it via the above link, this is expected.

So, it should be already fixed by now.

like image 125
gius Avatar answered Oct 14 '22 07:10

gius