The error sql72045 triggers while trying to import a BACPAC/DACPAC generated on a different server using SQL Server Management Studio.

As a part of our Server Management Services, we help our Customers to fix SQL related errors regularly.

Let us today discuss the possible causes and fixes for this error.

What causes error sql72045 ?

As updated earlier the error  triggers while trying to import a BACPAC/DACPAC generated on a different server using SQL Server Management Studio. A typical error message starts with the following lines:
 

This error generally triggers due to the following reasons:

1.The restore of the database from a big DACPAC/BACPAC file.
2.Switching to database level authentication rather than relying on server level logins.
3.The database being deployed exceeds the Max size of the selected Database Service tier.
4.Data types of column being altered.

How to fix error sql72045?

Let us now look at the methods to fix this error.

SQL72045 primarily triggers while we restore the database from a big DACPAC/BACPAC file. A data-tier application (DAC) is a logical database management entity that defines all of the SQL Server objects – like tables, views, and instance objects, including logins – associated with a user’s database.

Restoring from a larger file usually may take a long time and may cause the Timeout error. Further if the internet environment is unstable, script execution may also stop.

A solution here would be to use the sqlpackage.exe for the import. SqlPackage.exe is a command-line utility that automates the database development tasks like export, import, extract, publish etc. Further ensure the stability of the internet connection to avoid the termination of script execution in between.

Switching to database level authentication is another reason that trigger the SQL72045 message.  Executing the following T-SQL command will make the database partially contained.

sp_configure 'contained database authentication', 1;
GO
RECONFIGURE;
GO

Note that the contained databases no longer limits the control over access to the server to members of the sysadmin and securityadmin fixed server role. Thus its support is disabled by default as they have security implications.

The SQL72045 message also shows when the deployed database exceeds the Max size of the selected Database Service tier. To fix this, we need to Select a database tier that contains a Maximum database size that will accommodate the database that will be deployed.

Altered data types of column can also trigger this error. Solution here would be to rename the pre and post deployment scripts to do the work with a rename. Depending on the nature of the target you may of course need to take care of dropping and recreating foreign key constraints.

[Need any further assistance in fixing SQL errors? – We’re available 24*7]

Conclusion

In short, the error sql72045 triggers while trying to import a BACPAC/DACPAC generated on a different server using SQL Server Management Studio. Today, we saw how our Support Engineers fix this error.