Data Upgrade from AX 3.0/AX 4.0 to AX 2009

Hi,
In this post, I would like to explain you my experiences on the data upgrade from AX 3.0 and AX 4.0 to AX 2009. Please post your comments if you have any doubts on this……..


Data Upgrade from AX 3.0 to AX 2009

  1. Perform the Consistency Check for all the required modules in AX 3.0 application and proceed to upgrade only if there are no errors during the consistency check process else it will create problems during the process of running the upgrade checklist.
  2. Back up your existing database and application files.
  3. Delete the tables, AXOLDTONEWRECIDS and Sysdiagrams (System Table), as the same does not get transferred to the AX2009 database in the upgrade tool and later issues are thrown up.
  4. Import two .xpo files from the installation media to assist with data upgrade. -UpgradeColumnList.xpo, for 32-bit to 64-bit RecId field conversion. -LeftJustified.xpo, for removing any trailing spaces from fields. Note: To help improve performance, you can apply the LeftJustified.xpo on the database that you create in step 4 after you’ve used the Microsoft Dynamics AX DB Upgrade Preparation tool but before you start the Microsoft Dynamics AX 2009 AOS. See step 8.
  5. (Optional) To help improve performance, remove all user data and logs of Microsoft Dynamics AX 3.0. For example, clean up the SysDatabaseLog table.
  6. Create an empty database for Microsoft Dynamics AX 2009 in SQL Server 2005.
  7. (Optional) To help improve performance, set initial data and log file sizes so that they don’t increase while you perform the data upgrade process.
  8. (Optional) To help improve performance, set the recovery model to Simple for the Microsoft Dynamics AX 2009 Database.
  9. Run AXDBUpgrade.exe (The Microsoft Dynamics AX DB Upgrade Preparation tool). Note: To help improve performance, you can run this tool in Multithreaded mode. For example, to run this tool in 10 threads, enter AxDbUpgrade.exe P/10 at a command prompt.
  10. (Optional) Apply the LeftJustify file imported in step 2 to the Microsoft Dynamics AX 2009 database created in step 4.
  11. Back up your Microsoft Dynamics AX database. Your database is ready to be upgraded.
  12. Run the Microsoft Dynamics AX 2009 Setup file from the installation media. During installation, select the database that you created in step 4.
  13. Copy your upgraded customized file into the correct application directory.
  14. Start the AOS.
  15. Start the Microsoft Dynamics AX 2009 client. The Upgrade checklist is displayed automatically.
  16. Complete the steps in the Upgrade checklist to finish upgrading.
  17. Remember to take the backup of database and application files each and every stage of the upgrade checklist so that if there is any error, we can go back and start the process from that stage. this would save our time.
Data upgrade from AX 4.0 to AX 2009
  1. Perform the Consistency Check for all the required modules in AX 3.0 application and proceed to upgrade only if there are no errors during the consistency check process else it will create problems during the process of running upgrade checklist.
  2. Back up your existing database and application files.
  3. (Optional) To help improve performance, remove all user data and logs of Microsoft Dynamics AX 4.0. For example, clean up the SysDatabaseLog table.
  4. (Optional) To help improve performance, set initial data and log file sizes so that they don’t increase while you perform the data upgrade process.
  5. (Optional) To help improve performance, set the recovery model to Simple for the Microsoft Dynamics AX 2009 Database.
  6. Back up your Microsoft Dynamics AX database. Your database is ready to be upgraded.
  7. Run the Microsoft Dynamics AX 2009 Setup file from the installation media. During installation, select your existing Microsoft Dynamics AX database.
  8. Start the Microsoft Dynamics AX 2009 client. The Upgrade checklist is displayed automatically.
  9. Complete the steps in the Upgrade checklist to finish upgrading.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *