web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Creating multiple table indexes at once

(0) ShareShare
ReportReport
Posted on by 65

I received a list of missing AX 2012 indexes. I need to create these missing indexes in AX.

 Is there a way to do this via a job in AX or do I need to create each index manually in the AOT Tables?

Regards

Melvin

*This post is locked for comments

I have the same question (0)
  • nmaenpaa Profile Picture
    101,160 Moderator on at

    Hi Melvin,

    you already asked the same question a couple of days ago, and received some answers: community.dynamics.com/.../290498

    You can continue the discussion in that thread if you still have some open questions.

    If you don't have open questions anymore, please mark the answers as verified in that thread.

  • Verified answer
    A.Prasanna Profile Picture
    8,223 on at

    Hi Melvin,

    I had same issue , but the advice is not to create all the missing indexes .Adding Indexes wont always increase the Performance , some time there will be negative impacts.

    Refer these Links  : https://docs.microsoft.com/en-us/dynamicsax-2012/developer/best-practices-for-indexes 

                                 : https://community.dynamics.com/ax/f/33/t/226367

    For more information.

    Thanks & Regards,

    Amith Prasanna 

  • Verified answer
    guk1964 Profile Picture
    10,888 on at

    I would do it manually.

    You might want to analyse those first. Every added index takes longer to write to and bloats the database. (every insert, update and delete),

    Adding indexes to tables that are mainly used for write rather than read should be avoided e.g  InventTrans. There are many indexes that can often be usefully  be removed to improve performance. So look in the query plan to see how frequently the table is accessed..

    See these posts for some useful insights

    Many programmers get used to not including DataAreaId or Partition in a query because when they call a statement from X++, DataAreaId and Partition are not needed. When there is only one company, the query will return the same results as it does from within Dynamics AX. The issue with calling a SQL Query without adding DataAreaId and Partition is that most indexes on Dynamics AX tables start with DataAreaId and Partition. When you do not use DataAreaId and Partition, SQL cannot traverse the index to answer your query.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans