Lesson Learned #137: Running SQLPackage .NET Core

This post has been republished via RSS; it originally appeared at: Azure Database Support Blog articles.

This last week, I found an interesting issue. Our customer exported a database to bacpac file using SQLPackage .NET Core.

To import the data to another SQL Server, our customer tried to use SQLPackage for Windows but, they got an error reading the bacpac file with the following error message: File contains corrupted data. 


During our investigation we found that we have a known issue using SQLPackage for Windows to import a bacpac file that was created using SQLPackage .NET Core. As a workaround, download SQLPackage .NET Core software in your Windows Server Machine and execute it instead of SQLPackage for Windows or SQL Server Management Studio. 


We hope to have the fix very soon. 



REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.