I'm a DBA supporting Dynamics AX. In looking at a performance issue on our system I noticed that the clustered index on PRICEDISCTABLE is the fairly wide
index I_315PRICEDISCIDX rather then the primary key I_315RECID. I've contacted application team and they say this is not changed on their side.
Could anyone check and confirm this is standard configuration?
I_315ACCOUNTIDX nonclustered located on PRIMARY PARTITION, DATAAREAID, RELATION, ACCOUNTCODE, ACCOUNTRELATION, CURRENCY, ITEMCODE, ITEMRELATION, UNITID, QUANTITYAMOUNTFROM, FROMDATE, AGREEMENTHEADEREXT_RU
I_315AGREEMENTHEADEREXT_RUIDX nonclustered located on PRIMARY PARTITION, DATAAREAID, AGREEMENTHEADEREXT_RU
I_315DBA nonclustered located on PRIMARY PARTITION, DATAAREAID, ACCOUNTCODE, ACCOUNTRELATION
I_315GENERICCURRENCY nonclustered located on PRIMARY PARTITION, DATAAREAID, GENERICCURRENCY, RELATION, ITEMCODE, ITEMRELATION, ACCOUNTCODE, ACCOUNTRELATION, INVENTDIMID, UNITID
I_315ITEMDIMIDX nonclustered located on PRIMARY PARTITION, DATAAREAID, ITEMRELATION, ITEMCODE, INVENTDIMID, ACCOUNTCODE
I_315ITEMIDX nonclustered located on PRIMARY PARTITION, DATAAREAID, RELATION, ITEMCODE, ITEMRELATION, CURRENCY, ACCOUNTCODE, ACCOUNTRELATION, UNITID, QUANTITYAMOUNTFROM, FROMDATE
I_315PRICEDISCIDX clustered, unique located on PRIMARY PARTITION, DATAAREAID, RELATION, ITEMCODE, ITEMRELATION, ACCOUNTCODE, ACCOUNTRELATION, CURRENCY, INVENTDIMID, UNITID, QUANTITYAMOUNTFROM, RECID, FROMDATE, AGREEMENTHEADEREXT_RU, KRFSALESORDERCATEGORY
I_315RECID nonclustered, unique, primary key located on PRIMARY RECID