Errors SQL72014 & SQL72045 migrating Azure SQL.

Applies to: SQL Server Management Studio (SSMS), Azure Portal.

Date created: September 11, 2023.
 

Problem Description.
 

A user received the following error when using the Deploy Database dialog on SQL Server Management Studio to upload/migrate a database (bacpac) to Azure SQL Database.
 

Could not import package
Warning 0: A project which specifies SQL Server vNext CTP as the target platform may experience compatibility issues with Microsoft Azure Database v12.
Error SQL72014: .NET SqlClient Data Provider: Msg 40616, Level 16, State 1, Line 1 'admin' is not a valid login name in this version of SQL Server.
Error SQL72045: Script execution error. The executed script:
CREATE LOGIN [admin]
WITH PASSWORD = '********';
(Microsoft.SqlServer.Dac)

When the user used the Azure Portal to import the same bacpac to Azure SQL, he received the same errors as result.

Cause.

In this scenario, 'admin' is not a valid login name on Azure SQL Database despite it is valid on Microsoft SQL Server.

Workaround/Solution.

Try to remove the login name not supported (Admin in this case) at the database level before trying to migrate to Azure SQL Database again or before creating the bacpac.

I usually recommend users to use Azure Data Migration Assistant (DMA) to migrate a SQL Server database to Azure SQL Database, because it performs an assessment first and let you know things you need to fix prior to migrate to Azure SQL. Once all incompatibilities are fixed, DMA allows you to migrate with a couple of clicks as explained on this documentation.

.Send mail to webmaster@sqlcoffee.com with questions or comments about this web site.