75
In the past in for example AX2012 we were able to disable indexes on tables where we have a lot of data in, with a lot of indexes which are not used in our implementation.

This was especially useful for large tables, on which standard AX created a lot of indexes which are not useful for use (as we are using for example not all the functionality, or for example not the RU (Russion) localization). But we do have specific queries on other fields on which we want to add indexes.
We were able in the past to set the 'Enabled' flag in the AOT on the index to No, resulting in the index being dropped during Data dictionary syncrhonization.

In an Extension we are not able to change the 'Enabled' flag on an existing index.
This means we end up with tables with lots of indexes. Some usefull added in our implementation and a lot of unuseful indexes for our implementation, which:
- need to be updated while adding records (performance impact)
- taking a lot of disk space
- taking time to be rebuild during nightly index rebuilds

There are quite some tables in Dynamics containing indexes specifically for example for RU functionality when enabling that. So a lot of these indexes are not usful in a lot of implementations. But they are always added to every implementation...
Category: Development
STATUS DETAILS
Needs Votes

Comments

W

Wouldn't Microsoft consider taking this one under Review as well :-)?

Category: Development

W

Agree with comments on unitque indexes.

Category: Development

W

I agree with that Gert. Thanks for voting (y)!

Category: Development

W

I agree, but with a limitation, you should not be able to disable an unique index, since this is a breaking change.

Category: Development