mssql-server-linux:2017-CU container crashes when importing bacpac via sqlpackage

[seanknox]

Using microsoft/mssql-server-linux:2017-CU image + sqlpackage to import a bacpac file. Running Docker on Windows 10.

SQL Server crashes when it attempts to import a table with 14,828,059 rows. The container just dumps back to the command line. Command ran:

docker exec -it 0421fed8ac6779313662ec6a44c82eb4ad96fdf825562458f5f16f985caf7888  /tmp/sqlpackage/sqlpackage /a:Import /tsn:localhost,1433 /tdn:Database /tu:sa /tp:"yourStrong(!)Password"  /sf:/tmp/db/database.bacpac

Happy to provide more debug information if needed.

[seanknox]

Adding some more pertinent info in case anyone stumbles into this issue from the internet.

The same DB fails to import on SQL Server Express because it’s > 10GB. Perhaps the same issue here? The symptoms are the /opt/mssql/bin/sqlservr process is killed without any (seemingly) relevant logs in /var/opt/mssql/log/errorlog.

Here is the Dockerfile I’m using: https://gist.github.com/seanknox/19bacba43a504263c8d656a53678bc9b

• microsoft/mssql-server-linux:2017-CU9 image
• using sqlpackage to import a bacpac file

I don’t have a DB handy to share, but I bet any .bacpac file that yields a DB > 10GB will trigger this.

If the problem is a feature issue (DB being imported too big for this edition of SQL Server) that’s understandable, but there should be log output to indicate that.

[banerjeeamit]

Have you tried this with a Developer Edition container with the same result?