Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.


Symptoms

The performance of the GeneralJournalAccountEntry MainAccount field upgrade script is affected by the maintentenance index during the update in large volume enviornments (100 million records+), and the field is still updated in environments where the upgrade of that field may have already been completed in Microsoft Dynamics AX 2012 source environments.

↑ Back to the top


Resolution

The changes in the hotfix disable the GeneralJournalAccountEntry table ColumnStoreIdx index during the upgrade of the table to reduce the cost of updating the index during the update statement (the index is introduced in AX7, so the script will no-op with #2 check if it already exists).

 

The hotfix adds a check for MainAccount=0 to no-op enviornments where this field has already been upgraded, which will be most cases, as the field is introduced in Microsoft Dynamics AX 2012 as a performance hotfix.

 

The hotfix also reduces the transaction scope by batching the updates by ledger.

↑ Back to the top


More information

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained here in is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

↑ Back to the top


Article Info
Article ID : 4090117
Revision : 1
Created on : 2/15/2018
Published on : 2/15/2018
Exists online : False
Views : 178