Share via

Azure SQL Database

Fernando Gutierrez 265 Reputation points
2025-03-14T11:35:01.7933333+00:00

Hello

I need help, please:

I need to restore an Azure SQL Database I have in one tenant to another. These tenants have no connection or visibility into each other. They are different.

I already created the rest of the SQL database within the same Azure.

Then I downloaded it locally as a bacpac file, using Export Data Tier.

I uploaded it to a storage location in the tenant where it should be located, the destination tenant, but when I try to import that database into SQL Server, it won't let me and I get an error.

SQL Server on Azure Virtual Machines
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sai Raghunadh M 2,885 Reputation points Microsoft External Staff
    2025-03-14T14:02:25.42+00:00

    Hi @ Fernando GutierrezRestoring an Azure SQL Database from one tenant to another can be challenging, especially when the tenants are isolated. Based on your steps, it seems you're on the right path with the BACPAC file method. However, the error during import could be caused by some common issues.

    Here are few suggestions to help you troubleshoot:

    Verify that the BACPAC file was uploaded successfully to the Azure Storage account in the destination tenant. Ensure the file is fully uploaded and there are no issues with its integrity.

    In the destination tenant, you can use the Azure Portal to import the BACPAC file into a new Azure SQL Database. Follow these steps:

    Navigate to the Azure SQL Server: In the destination tenant, go to the SQL server where you want to restore the database.

    Import from BACPAC:

    • Go to the SQL Databases section.
    • Click + Add or Import.
    • Select Import from BACPAC and specify the BACPAC file URL from the storage account in the destination tenant.

    Ensure you select the correct database server and configure the appropriate settings (such as database name, resource group, etc.).

    If you are using a private storage account or if the destination tenant doesn’t have full access to the storage account where the BACPAC file is located, you may need to provide access via a SAS token.

    • Generate SAS token: In the storage account, generate a Shared Access Signature (SAS) token with the necessary permissions (Read and List).
    • Attach the SAS token when specifying the BACPAC file’s URL during the import process.

    If you could provide the specific error message, it might offer more insights. Common errors include schema compatibility issues, missing permissions, or unsupported features.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.