Guess my next class should be on Allbase. :) Got this e-mail in-house
and am hoping someone on the list can help me out, since our Allbase
guru left. (Names and confidential info have been deleted per company
policy.)

TIA,
Patrick (forwarded text follows)
----------
From: JW
To: PS
Cc: SA
Subject: FW: PD_PREM Indexes not working
Date: Wednesday, July 22, 1998 4:07PM

Who is the current in-house Allbase expert?  This information is coming
from SB who is a contractor working on [some of our] projects.  I
would like to know if her concerns are accurate and if there is anything
that can be done regarding her recommendations?   Please let me know.

Thanks!
 ----------
From: SB
To: JW
Subject: PD_PREM Indexes not working
Date: Wednesday, July 22, 1998 3:48PM

F.Y.I.,

I checked out the SYSTEM.INDEX table to check on the INDEX performances.
I noticed the CCOUNT (determines the efficiency of the INDEXES) was
larger than the NPAGES  and NROWS counts. Translated,  the indexes are
no longer efficient to use and are being bypassed (not used).  Normally,
The INDEX should be dropped and recreated whenever CCOUNT is more than
half NROWS.

This is why we are receiving slow responds when accessing VW_PD_PREM.
The CCOUNT are 58,787,831 (index 1) and 1,658,887 (index 2) while NROWS
is only 58,8009.

Recommend dropping & recreating INDEXes (1) I2_PD_PREM & (2) I3_PD_PREM
at the minimum. All the indexes really need to be dropped & recreated to
improve performance.

Let me know if you need any data/info.

S
--
Patrick Santucci
Technical Services Systems Programmer
KVI, a division of Seabury & Smith
Visit our site! http://www.kvi-ins.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If they try to rush me, I always say, 'I've only got
one other speed -- and it's slower.'"    ~ Glenn Ford