Import a database
You can use Microsoft Dynamics Lifecycle Services (LCS) to import a database for Microsoft Dynamics 365 for Finance and Operations into a sandbox user acceptance testing (UAT) environment.
Self-service import database
To import a database prepared from a developer environment to a standard user acceptance test (UAT), or a database previously exported from a UAT environment, follow the steps outlined below:
- Go to your target sandbox Environment Details page, and select the Maintain > Move database menu option.
- Select the Import database option and choose your source database backup (.bacpac format) file from the Asset Library.
- Note the warnings. Review the list of data elements that are cleaned up from the backup file.
- The import operation will begin immediately.
- After the import operation is completed, you must Sign off on the operation before you can perform another servicing operation, such as package deployment, database movement, or upgrade.
Import operation failure
If the import operation isn't successful, you can do a rollback. If you select the Rollback option after the initial failure of the operation, your target sandbox environment is restored to the state that it was in before the import began. The rollback operation is made available by the Microsoft Azure SQL Database point-in-time restore capability for restoring the database. Rollback is often required if a customization that is present in the target sandbox can't complete a database synchronization with the newly imported data.
To determine the root cause of the failure, download the runbook logs by using the available buttons before you start the rollback operation.
Data elements that require attention after import
Specific activities must be completed when you import a database backup into a sandbox UAT environment. Here are some examples:
- Make sure that email capabilities are correctly reconfigured or turned off, according to your requirements.
- Make sure that integration settings are turned on or off, according to your requirements.
- Make sure that Application Object Server (AOS) servers are added back to required batch groups.
- Make sure that system Help and task guides are reconnected.
- Make sure that batch jobs are set to a status of Waiting.
- Make sure that users are re-enabled.
The system admin account in the target environment (Admin user ID) is reset to the value that is found in the web.config file in that environment. This account should be the same as the admin account from LCS. To preview which account this account will be, visit the Environment details page for your target sandbox in LCS. The value that was selected in the Environment Administrator field when the environment was first deployed is updated to the system admin in the transactional database. Therefore, the tenant of the environment will be the tenant of the environment admin.
If you've used the Admin User Provisioning Tool on your environment to change the web.config file, the value might not match the value in LCS. If you require that a different account be used, you must deallocate and delete the target sandbox, redeploy, and select another account. You can then do another database refresh action to restore the data.
Steps to complete after a database import for environments that use Retail functionality
If you copy a database between environments, the copied database won't be fully functional until you run the Environment reprovisioning tool to make sure that all Retail components are up to date.
Follow these steps to run the Environment reprovisioning tool.
- In your project's Asset Library, in the Software deployable packages section, click Import.
- From the list of shared assets, select the Environment Reprovisioning Tool.
- On the Environment details page for your target environment, select Maintain > Apply updates.
- Select the Environment Reprovisioning tool that you uploaded earlier, and then select Apply to apply the package.
- Monitor the progress of the package deployment.
Some environment specific records cannot be moved along with the database from the source to the target environment. The following records are not moved to the target environment:
- Retail Self-Service installers
- Retail Cloud Scale Unit channel database configuration record
Database refresh and Retail Cloud Scale Units
As part of database refresh, scale unit channel database records (in the Channel Database form) cannot be moved across environments since they represent environment specific configuration.
For Retail Cloud Scale Units, you can regenerate the channel database record by issuing a re-deployment of your scale units in LCS. For more information, see Database refresh and Initialize Retail Cloud Scale Unit.
Database refresh and Retail Self-Service installers
Self-service installers are stored in environment specific storages that cannot be moved along with the database.
Installers are uploaded to the environment as part of a deployable package. The application and binary packages provided by Microsoft will contain the Microsoft provided installers. The Retail Deployable package produced by extensions through the Retail SDK will contain the extended installers. To make installer section available after database refresh, please apply the desired deployable package to the environment after database refresh.
Import is denied for environments that run Platform update 3 or earlier
The import database process can't be completed if the environment is running Platform update 3 or earlier. See the list of currently supported platform updates.
Send feedback about: