Sql Azure - backpack 0 megs

juan maximiliano aguilar abanto 541 Reputation points


I export a Sql Azure bacpac in a Azure storage, but It always weighs 0 megs.


I don't understand, if when I download it in a machine it weight 1.5 megs.

Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,536 questions
0 comments No comments
{count} votes

Accepted answer
  1. juan maximiliano aguilar abanto 541 Reputation points

    I understand the problem..

    This is an expected behavior, this 0 byte file is used to check whether it has permissions to your storage account container. The service will not write out the full BACPAC until the export is complete.

    After I wait 10 minutes the sizes of the backup was: 487.29 KiB

    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Vaibhav Chaudhari 38,666 Reputation points

    You may post this question in a dedicated forum for Azure SQL DB in below. This QnA forum currently doesn't support Azure SQL DB related question.


    If the response helped, do "Mark as answer" or upvote it

    • Vaibhav
    0 comments No comments

  2. Mike Ubezzi 2,776 Reputation points

    As stated, can you ask this question in the Azure SQL Database MSDN forum but, I am going to respond to this issue here. This is potentially an Azure Storage issue that is manifesting itself with a .bacpac file. Are you seeing this behavior when you view the .bacpac file in the Azure Portal only? Have you attempted to view this same file in your Azure Storage account with the Azure Storage Explorer desktop client? If not, can you please download/install the client and navigate to the .bacpac file and see if file details are displayed correctly? Please see: Manage Azure Blob Storage resources with Storage Explorer for a full walkthrough of using storage explorer. Like I said, this could be a limitation of viewing the same file through the portal but it would be good to have a screen capture or additional details of this behavior. Thank you!

    0 comments No comments