I'm investigating a performance issue at a customer's site
and I've narrowed
it down to a single query involving inventsum & inventdim.
The problem is pretty strange, needing to reindex every now and then.
For many reasons it's advised to have a clustered index on every table
(would avoid the fragmentation i'm seeing now for example) but inventsum and
inventdim have no clustered index, and inventdim hasn't even got a primary
key (dimidx is defines as allowduplicates=no)
But I'm wary of changing these, because I assume since these are very core
tables, navision/ms evaluated the options and picked this design for a reason.
Then again I don't see how adding a clustered index on inventdimid (always
increasing, never gets changed) could hurt that much
Anyone have any insight?
Could I create trouble elsewhere if I add those primarykeys and clustered
indexes? Are these design decisions maybe taken because oracle needs to be
supported?
Sharing the knowledge on Axapta.
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
- [Axapta-Knowledge-Village] Clusteredindex ... TVG Tom Vergote
-