Setting up Docker Containers for Dynamics 365 Business Central

Step 1: Please enable Hyper V and Container features from Programs and Features

https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v

You may need to restart the computer.

Step 2: Install docker

Once you finished installed Docker switch it to Windows.
Right click on the docker icon on the bottom right hand corner.

You may need to restart the computer to complete the action.

Step 3: Run the PowerShell ISE as an Administrator

Step 4: You can use below Docker commands to check whether it’s working.

Docker version 

Docker help

You can see more functions that you can use in the future.

Step 5: Use Docker pull command.

Docker pull mcr.microsoft.com/businesscentral/sandbox:au-ltsc2019

Use below url for more updates

https://hub.docker.com/_/microsoft-businesscentral-sandbox

Examples (ltsc2016):

• docker pull mcr.microsoft.com/businesscentral/sandbox gives you the latest Business Central Sandbox Container worldwide version
• docker pull mcr.microsoft.com/businesscentral/sandbox:dk gives you the latest Business Central Sandbox Container DK version
• docker pull mcr.microsoft.com/businesscentral/sandbox:13.1.25940.0-us gives you a specific Business Central Sandbox build with the US version

Examples (ltsc2019):

• docker pull mcr.microsoft.com/businesscentral/sandbox:ltsc2019 gives you the latest Business Central Sandbox Container worldwide version
• docker pull mcr.microsoft.com/businesscentral/sandbox:dk-ltsc2019 gives you the latest Business Central Sandbox Container DK version
• docker pull mcr.microsoft.com/businesscentral/sandbox:13.1.25940.0-us-ltsc2019 gives you a specific Business Central Sandbox build with the US version

Once it finished you will see below message. Don’t run any other commands until it completely finished.

Step 6: Check your Image

By using below command, you can see all the images you are having

 Docker images

Step 7: Install NavContainerHelper

install-module navcontainerhelper -force

Once you run that command you will see below message.

Select Yes and then it will start installation 

You may need to reload power Shell to work with new function.

Step 8: Allow permissions to install the rest.

 Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Confirm -Force

Select Yes to All.

Step 9: Create NAV-Container

You can search New-NavContainer from the window on your right-hand side or type the command.

I would recommend use the wizard.

New-NavContainer -containerName BC365 -accept_eula -accept_outdated -assignPremiumPlan -auth NavUserPassword -doNotExportObjectsToText -imageName mcr.microsoft.com/businesscentral/sandbox:au-ltsc2019 -includeAL -includeCSide -licenseFile "D:\License.flf"‪‪‪ -memoryLimit 4G -shortcuts Desktop -updateHosts

Mandatory (containerName, accept_eula, assignPremiumPlan, auth, imageName, doNotExportObjectsToText(This will Speed up the process), includeAL, licenseFile(If you select include AL), memoryLimit)

Once it’s finished you will see below detail screen

Then it will add below short cuts on your desktop if you enabled the Boolean when creating the container.

Data is bulk loaded at this point in deployment execution #SQL72012 #SQL72016 #SQL72045 #Execution Timeout Expired #Azure SQL to On-promise

Last week I got a task to create a local copy from an Azure SQL Database. It was fine few months back. However, I got below error message saying “Data is bulk loaded at this point in deployment execution”.


TITLE: Microsoft SQL Server Management Studio
------------------------------
Could not import package.
Warning SQL72012: The object [nav-uat_Data] exists in the target, but it will not be dropped even though you selected the 'Generate drop statements for objects that are in the target database but that are not in the source' check box.
Warning SQL72012: The object [nav-uat_Log] exists in the target, but it will not be dropped even though you selected the 'Generate drop statements for objects that are in the target database but that are not in the source' check box.
Error SQL72016: Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
Error SQL72045: Script execution error.  The executed script:
/*
Data is bulk loaded at this point in deployment execution
*/
 (Microsoft.SqlServer.Dac)
------------------------------
ADDITIONAL INFORMATION:
Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServ





Solution


You can use the latest version of the SqlPackage.exe command line tool with a larger timeout.
DacFX supports various database deployment and management scenarios for SQL Server and Microsoft Azure SQL Databases including extracting / exporting a live database to a DAC package, deploying a DAC package to a new or existing database, and migrating from on - premise SQL Server to Microsoft Azure. This functionality is exposed via the DACFx managed API. DACFx can target SQL Server 2008, 2008R2, 2012, 2014, 2016 CTPs and Microsoft Azure SQL Databases. DACFx also provides the command-line utility SqlPackage.exe for creating and deploying.dacpac and .bacpac packages. DACFx supports scenarios provided by SQL Server client tooling including SQL Server Data Tools and SQL Server Management Studio.
 You download and use the latest DacFx release from the below link:

https://www.microsoft.com/en-us/download/details.aspx?id=51941

NOTE: If you are on an x64 machine, you will need to install both the x64 and x86 versions of the MSIs above.

After you have installed Microsoft® SQL Server® Data-Tier Application Framework

There are some commands you have to execute
Step 1
Run Command as an Administrator. Use cd command to change the path





This will change the path from system32 to the path you want to execute the .exe.


Step 2

Execute the command.
Use the below example command line:
sqlpackage.exe /Action:Import /tsn:servername /tdn:databasename /tu:adminuser /tp:adminpassword /sf:export.bacpac /p:CommandTimeout=1800

sqlpackage.exe /Action:Import /tsn:MBS /tdn:nav-uat /tu:sa /tp:password /sf:"D:\MBS\MBSUAT11042019.bacpac" /p:CommandTimeout=1800