This post has been republished via RSS; it originally appeared at: Azure Database Support Blog articles.
Our customer was unable to import a bacpac file from Azure blob storage via portal, failing with error: "Import operation interrupted because insufficient local disk is available for bacpac file. Please use SSMS or SqlPackage to complete the operation."
As the error message shows, the local disk is insufficient to host the bacpac file, based on the documentation, the required disk space should be up to 3 times the size of the DB. Import a BACPAC file to create a database in Azure SQL Database - Azure SQL Database | Microsoft Learn
The machines processing import/export requests submitted through portal or PowerShell need to store the bacpac file as well as temporary files generated by Data-Tier Application Framework (DacFX). The disk space required varies significantly among DBs with same size and can take up to three times of the database size. Machines running the import/export request only have 450GB local disk space. As result, some requests may fail with "There is not enough space on the disk" error. In this case, the workaround is to run SqlPackage on a machine with enough local disk space. When importing/exporting databases larger than 150GB, use SqlPackage to avoid this issue.
In this situation, using SQL Server Management Studio or SQLPackage to export this data was the solution for our customer: SqlPackage.exe - SQL Server | Microsoft Docs
The following document has examples on how to import the DB: Using SQLPackage to import or export SQL Server and Azure SQL DB - Microsoft Tech Community