Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
----LNX_Thu_Mar_06_2003_09:59:39_V3.33--
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
=
is the reorganization of indexes needed too maintain good performance?
Do you reorganize (drop/create) your indexes periodically?
IDS versions 7.31.UC4, 7.31.xDx and 9.30.UCx.
=
Our experiences so far:
- Continous growth of indexes with leading char-columns when the column
values grow (like IDs getting higher and higher or some kind of timesta=
mps).
In that case we have to recreate the index for space reasons.
- Indexes on columns with many inserts/updates/deletes tend to get 'bad' =
-
in one case that seemed to cause locking problems under high systemload=
=2E
Do you think that the fragmented indexes can really cause such problems=
?
- Indexes tend to grow (and get fragmented) - does reorganization save us=
from giving the database more buffers and more CPU cycles - or is there=
almost no difference?
=
Any experiences or suggestions are appreciated.
=
Regards,
Andreas Kutsche
=
=
------------------------------------------------
SPAR Oesterreichische Warenhandels-AG
Hauptzentrale
Europastra=DFe 3
A-5015 Salzburg
=
Telefon : +43 662 4470 24423
E-Mail : Andreas.KUTSCHE@spar.at
Internet: http://www.spar.at
------------------------------------------------
=
----LNX_Thu_Mar_06_2003_09:59:39_V3.33----
Yes
Indexes do need to be reorganized periodically. Fragmented indexes can be more
of a performance issue than fragmented tables. If you are using indexes
heavily, set up a schedule to reorganize the high use indexes where you are
doing a lot of inserts and deletes.
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.