Upgrade from AX 3.0 to AX 2009

This topic lists the high-level steps involved in upgrading from Microsoft Dynamics AX 3.0 to Microsoft Dynamics AX 2009.

1. Back up your existing database and application files.
2. 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.
3. (Optional) To help improve performance, remove all user data and
   logs of Microsoft Dynamics AX 3.0. For example, clean up the
   SysDatabaseLog table.
4. Create an empty database for Microsoft Dynamics AX 2009 in SQL Server 2005.
5. (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.
6. (Optional) To help improve performance, set the recovery model to Simple for the Microsoft Dynamics AX 2009 Database.
7. 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.
8. (Optional) Apply the LeftJustify file imported in step 2 to the Microsoft Dynamics AX 2009 database created in step 4.
9. Back up your Microsoft Dynamics AX database. Your database is ready to be upgraded.
10. Run the Microsoft Dynamics AX 2009 Setup file from the installation
    media. During installation, select the database that you created in
    step 4.
11. Copy your upgraded customized file into the correct application directory.
12. Start the AOS.
13. Start the Microsoft Dynamics AX 2009 client. The Upgrade checklist is displayed automatically.
14. Complete the steps in the Upgrade checklist to finish upgrading.

Ax Database Configuration Checklist Part 2

Tempdb database storage configuration

q Determine total size of data and transaction log required for tempdb to avoid autogrow, and number of data files required based on # of processors (logical or physical).

How:

Determine the number of processors exposed to SQL Server. Unless you are using an affinity mask (not covered here), this is the total number of processors you see in the Windows Task Manager Performance tab.

Why:

SQL Server creates one visible scheduler (for processing user requests) for each processor, and we generally want to maintain one tempdb data file per processor. This recommendation is based on performance testing on the Dynamics AX OLTP workload.

Ax Database Configuration Checklist part 1

Welcome to the Dynamics Ax Performance Team’s blog.  We’re putting together a team introduction and hope to have it posted within the next week or so.  The first entries will discuss SQL Server 2005 configuration and Best Practices for Dynamics Ax, but we’ll be covering a much wider range of topics over the coming months, such as Dynamics AOS configuration, X++ profiling, and leveraging new features of SQL Server 2008.

Get and show available columns from the selected table

SQL untuk mendapatkan informasi kolom dari table yang dipilih

SELECT column_name, data_type, character_maximum_length, is_nullable, column_default FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_NAME = strTABLE

strTABLE =  nama table yang dimaksud

Configuration in Title bar

Configuration in title bar

One common complain with Dynamics Ax 4.0 is that it is not possible for the user to determine in which environment they are working.

reset temporary table

You can use 3 ways: 1 is slow, 2 are fast.

How to send data to Excel

static void Send_toExcel(Args _args) {

   SysExcelApplication         ExcelApplication;
   SysExcelWorkBooks           ExcelWorkBooks;
   SysExcelWorkBook            ExcelWorkBook;
   SysExcelWorkSheets          ExcelWorkSheets;
   SysExcelWorkSheet           ExcelWorkSheet;
   SysExcelRange               ExcelRange;
   CustTable                   ct;
   int                         row;
   ;
 

save and open word document

static void WordTemplateOpen()
{
COM wordApp;
COM wordDocuments;

selection of several records in a grid (Multi select)

To unnecessary code to avoid duplications, we can even with a for-loop work:

Create Progress Indicators

Use a progress indicator during operations that take more than 2 seconds.

• Use an hourglass mouse pointer if the process takes 2-7 seconds.
• Use a progress bar if the process takes 8 seconds or more.