Import SQL bacpac file results in no data or tables via Azure portal

Zuuber 185 Reputation points
2023-10-29T12:51:06.5366667+00:00

Hi

I'm trying to import an SQL bacpac file into Azure hosted SQL database.
I go to 'Import database' via 'SQL Server' resource, select bacpac file then the import seems to complete but the database contains no data or tables, what am I doing wrong? The same also occurs if I select 'Export Data-Tier Application' via Management Studio.

But, if I use Management Studio and connect to the Azure hosted database then select 'Import Data-Tier Application' it works.

Why does the import not work via Azure Portal or via Man Studio when selecting 'Export Data-Tier Application'?

Any help would be greatly appreciated, thank you.

Azure SQL Database
SQL Server | Other
0 comments No comments
{count} votes

Accepted answer
  1. Konstantinos Passadis 19,586 Reputation points MVP
    2023-10-29T18:37:27.77+00:00

    Hello @LeonT !

    Welcome to Microsoft QnA!

    I can see your issue with SQL been there trust me !

    First of all

    https://learn.microsoft.com/en-us/azure/azure-sql/database/database-import?view=azuresql&tabs=azure-powershell

    have you seen the Limitations :

    • Importing to a database in elastic pool isn't supported. You can import data into a single database and then move the database to an elastic pool.
    • Import Export Service does not work when Allow access to Azure services is set to OFF. However you can work around the problem by manually running SqlPackage from an Azure VM or performing the export directly in your code by using the DacFx API.
    • Import does not support specifying a backup storage redundancy while creating a new database and creates with the default geo-redundant backup storage redundancy. To work around, first create an empty database with desired backup storage redundancy using Azure portal or PowerShell and then import the .bacpac into this empty database.
    • Storage behind a firewall is currently not supported.
    • During the import process, do not create a database with the same name. The import process creates a new database of the specified name

    Second , in my env it worked from the Sql Management Studio select deploy to Azure SQL .... it was the only way it worked correctly !


    I hope this helps!

    Kindly mark the answer as Accepted and Upvote in case it helped!

    Regards

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

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.