cncjay
Well Known Member
Hey All,
In an effort to manage indexes for E1 on MSSQL server 2008 R2,
Question 1: After careful monitoring, if it is determined that some of the indexes on JDE delivered tables are simply not being used - can I delete them ?
A contractor E1 developer recently mentioned that, for example, F4316 has the following indexes:
F4316_PK
F4316_1
F4316_4
F4316_5,
If I was to delete F4316_4 because it has not been in use, then the existing indexes get renumbered which will cause havoc.
I have doubts about the remaining indexes getting renumbered - can anyone confirm this, if it is a fact or a myth.
Question 2:
The SQL query analyzer will often recommend indexes that don't exist for standard delivered JDE tables, is this safe to do outside of E1? I've done a few so far and they 'seem' to be helping, I can't tell if there's a negative impact. Any best practices I should be following when creating additional indexes?
Thanks a million in advance
In an effort to manage indexes for E1 on MSSQL server 2008 R2,
Question 1: After careful monitoring, if it is determined that some of the indexes on JDE delivered tables are simply not being used - can I delete them ?
A contractor E1 developer recently mentioned that, for example, F4316 has the following indexes:
F4316_PK
F4316_1
F4316_4
F4316_5,
If I was to delete F4316_4 because it has not been in use, then the existing indexes get renumbered which will cause havoc.
I have doubts about the remaining indexes getting renumbered - can anyone confirm this, if it is a fact or a myth.
Question 2:
The SQL query analyzer will often recommend indexes that don't exist for standard delivered JDE tables, is this safe to do outside of E1? I've done a few so far and they 'seem' to be helping, I can't tell if there's a negative impact. Any best practices I should be following when creating additional indexes?
Thanks a million in advance