epost
Active Member
DBA\'s XE Index Concerns
Getting my first chance to dig around on an XE install and have a few
questions/concerns. I was a bit surprised to find so many indexes at first
on a "tables" tablespace. I soon found out that these are all primary keys.
A count of indexes shows that in addition to the 2000 or so PK indexes there
are another 2000+ indexes on the data tables in the indexes tablespace.
Well that happens to be about the same amount of indexes in B733.1. JDE was
already plagued by a number of completely redundant/useless indexes and now
it appears that they have added on to the problem. I've only been digging
around for a few minutes so maybe I have missed something (maybe a lot more
tables...?). For anyone who doesn't know, more indexes means slower inserts
and updates. My question is if anyone has moved these PK's to the index
tablespace? Next question is if anyone has ever done any tuning by removing
indexes that are redundant in that they offer almost no increase in
selectivity over existing indexes?
Thanks,
Ethan Post
------------------------------------------------------------------------------
This e-mail is intended for the use of the addressee(s) only and may contain privileged, confidential, or proprietary information that is exempt from disclosure under law. If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy. Thank you.
==============================================================================
Getting my first chance to dig around on an XE install and have a few
questions/concerns. I was a bit surprised to find so many indexes at first
on a "tables" tablespace. I soon found out that these are all primary keys.
A count of indexes shows that in addition to the 2000 or so PK indexes there
are another 2000+ indexes on the data tables in the indexes tablespace.
Well that happens to be about the same amount of indexes in B733.1. JDE was
already plagued by a number of completely redundant/useless indexes and now
it appears that they have added on to the problem. I've only been digging
around for a few minutes so maybe I have missed something (maybe a lot more
tables...?). For anyone who doesn't know, more indexes means slower inserts
and updates. My question is if anyone has moved these PK's to the index
tablespace? Next question is if anyone has ever done any tuning by removing
indexes that are redundant in that they offer almost no increase in
selectivity over existing indexes?
Thanks,
Ethan Post
------------------------------------------------------------------------------
This e-mail is intended for the use of the addressee(s) only and may contain privileged, confidential, or proprietary information that is exempt from disclosure under law. If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy. Thank you.
==============================================================================