First published on MSDN on Jan 28, 2019
The latest version of SQLPackage supports migration to Azure SQL Managed Instance (MI) from multiple SQL sources such as Azure SQL Databa...
Updated Mar 14, 2019
Version 2.0
Blog Post
Hi,
I think I have a solution that will satisfy you:
SQLPACKAGE.EXE has a special parameter to specify an external model.xml file
(https://docs.microsoft.com/en-us/sql/tools/sqlpackage/sqlpackage-import?view=sql-server-ver16)
The .bacpac file, on the other hand, is actually a ZIP, which inside contains a script for creating database objects (model.xml) and data.
All you need to do is open the .bacpac with 7zip, winrar or a similar program, extract the model.xml file from it and edit it removing external users, external data sources and external tables.
Then use the sqlpackage.exe command more or less like this:
PS C:\Program Files\Microsoft SQL Server\160\DAC\bin> .\sqlpackage.exe /a:Import '/sf:C:\Users\User\Downloads\DB.bacpac' /tsn:'ManagedInstanceServer.acbcc13fa309.database.windows.net' /tdn:'TargetDB' /tu:'ManagedInstanceUsername' /tp:ManagedInstancePassword /mfp:C:\CustomModel\model.xml
Actually, the proper tool for migrating databases from Azure SQL Database to Azure Managed Instance is seriously missing.
Exporting and importing a bacpac file with a 1.5TB database takes about 110h.