Skip to main content
Dynamics 365

Backup/restore the Model database or export/import the Model Store?

In this post I would like to clarify the differences between doing a backup/restore of the Model database, and doing an export/import of the Model Store.

Since version 2012 R2, and the separation of the application elements in a different database (the Model database), it is technically possible to restore this database separately. However, this is not the best practice, as documented in the “Deploying Customizations Across Microsoft Dynamics AX 2012 Environments” white paper.

The reasons why the recommended process is to export/import the Model Store are the following:

  1. When importing the Model Store, a validation is performed on the Element IDs, giving visibility of possible conflicts.
  2. It is possible (and recommended) to import the Model Store into a temporary schema, which reduces the application’s downtime. This technique also allows you to go back to the previous Model Store quicker than restoring a database backup, in case a problem is detected and a rollback is necessary.

In addition, you will find information on the differences between XPO, AXModel, and AXModelStore here.

I hope this is helpful!


With the help of Johan Broberg.