Moving between Microsoft Dynamics AX 2012 Environments
It is common practice to restore a Microsoft Dynamics AX database from one environment into another environment for testing and development purposes. In most cases, this is not a problem but there are circumstances that need to be considered to get the restored database
functioning. The scope of this document covers settings such as server names, domain names, user accounts, and URLs that may need to be changed in the new environment.
In Microsoft Dynamics AX® 2012 RTM (6.0), the application code files are stored in the same database as the transactional business data and in Microsoft Dynamics AX® 2012 R2 (6.2) there is a separate _model database. Both database implementations require further
planning to move environments.
There are special circumstances where there are AOT based metadata and matching SQL database records that need to be moved together, such as customized security or workflow objects.
Consider the following scenarios where users may need to restore a Microsoft Dynamics AX database to a different environment:
- Testing a Microsoft Dynamics AX service pack, rollup, or full version upgrade.
- Bringing Microsoft Dynamics AX 2012 data in house for testing or development.
- Restoring a copy of the production database into a test or development environment to
work with the most recent changes.
- Moving a production database from one Active Directory domain to different production
Active Directory domain environment.
In most scenarios, users should have the base Microsoft Dynamics AX 2012 software installed in the new environment and running at the same service pack and rollup version as the environment where the database was backed up. This would not apply to scenarios where users are testing a service pack, rollup or full version upgrade.
At a high level, the process for moving the database from one environment to another will follow these steps:
- Restore the database and set proper SQL permissions.
- Provide correct Microsoft Dynamics AX
user credentials to allow users to connect and login with a client.
- Configure the base system functionality for those setting which may have changed.
- Install or configure additional components such as Business Intelligence and Enterprise
The specific requirements of a user’s particular scenario may include additional steps or steps in a different order. This document is designed outline common considerations. Having a good understanding of the installation process and all the integrations and touch points will aid users in adapting the process to their needs.
This is a summary of the full document attached below, which has also been updated to add additional information on Microsoft Dynamics AX® 2012 R2 (6.2)
We're always looking for feedback and would like to hear from you. Please head to the Dynamics 365 Community to start a discussion, ask questions, and tell us what you think!