Transfer AX 2012 R3 Database to a New SQL Server

(0) Share

Report

Posted on by Manmeet Kaur

Hello AXers

I need to move my AX 2012 R3 database to a new SQL Server machine. Are there published/blessed steps to do that?

I can think of the following, but not sure if this will transfer the Enterprise Portal, SSRS reports and Management Reporter:

1. Stop Management Reporter Service

2. Stop AX Service

3. Backup the dynamics databases - DynamicsAX, Baseline, Model and ManagementReporter

4. Restore on new server and assign permissions

5. Launch AX Server Configuration and Create a new profile with new database connection

6. Start the services

How do SSRS reports get transferred?

Any special settings needed for Enterprise Portal?

Any special settings change for management reporter?

You guidance is always appreciated.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

syed baber 11,633 on at

Like (0)

Report

Hi CJ,

The steps you mentioned looks good to me. If you are going to use the same AOS to connect to the database on new machine, then nothing much needs to be changed. I assume that you are also going to restore the model store database, in that case all the application objects including SSRS reports will get imported. You just need to deploy the reports to your report server. You can use the power shell command for bulk deployment of SSRS reports. Below link explains how to do that:

technet.microsoft.com/.../dd309703.aspx

For management reporter, you also need to point to the new database server and then you may need to generate the data again after updating the machine.

Please let me know if you have further queries.

Thanks,

Baber.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

consider Model Store Export Import

Please read through following link for more details

technet.microsoft.com/.../hh433530.aspx

If installation of two environments (Source and target) are identical then you will not have any issue everything will be configured

Please verify and update us with your findings

Was this reply helpful? Yes No
Suggested answer

Faisal Fareed 10,796 User Group Leader on at

Like (0)

Report

Complete modelStore install will give you more verification of everything you have in source database and want to move to destination database. You can check Install ModelStore commands from technet, easy to get.

However, if you are planning to update your destination machine with source you just need to make sure few more steps in addition to what you have mentioned.

1. Take destination database and model database backups to be on safe side, if something goes wrong you can easily restore these backup again.

2. Take screen shots of Repor server configuration, Enterprise Portal and Management reporter from source and destination servers.

If these settings are different in destination server then you need to update them in destination server with these screen shots backup.

3. You need to deploy all SSRS report again in destination server

4. You need to deploy EP if there is a difference in source and destination settings. Please do to make sure everything is correct.

5. You also need to take care of Email Parameters, Batch Server and System service accounts settings if these are different in both machines.

Was this reply helpful? Yes No
Manmeet Kaur 2 on at

Like (0)

Report

I tried this on our test environment. I am not able to create a new server configuration, it gives an error for WSDL Port. The WSDL port text box is greyed out and clicking the OK or Apply button gives "Please enter an integer between 1024 and 65535" message. I can save the new configuration or make it the active one.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

One other thing that needs to be done is to create the CREATETEMPDBPERMISSIONS stored procedure in the master database. This runs when SQL Server starts to assign appropriate permissions to the AOS service account to tempdb. Various things will fail with tempdb errors if this isn't present.

Go to the old database server and find the procedure in the master database, generate the create script, modify if needed, and run it on the new server.

Was this reply helpful? Yes No