Re: oncheck performance issues
Posted in 1996
I can tell you that oncheck -cI will be slower as it will now
verify that the key value in the index will match the value of the
column in the table that that was indexed. This verification didn't
happen 5.x. For example: table1 has (col1 int, col2 char(5)) and
has index idx_one on col1. So as it scans idx_one it finds a key
value of 12 which has as it's rows that have a value of 12 in col1
as row 5 and row 6. Oncheck will now read rows 5 and 6 and make sure
that the data for col1 is indeed 12. That is a lot more processing
then 5.x tbcheck did. When the value in the data didn't match
the value in the index you would get things like rowid not found
for delete when you would try to delete these rows and such.
Jacques
Joe Lumbley wrote:
>
> Folks,
>
> Has anyone else noticed slow performance with the 7.1X versions of oncheck?
> Seems to be running very slowly and going into wait states on most if not
> all options.
>
> Does anyone have any insight into this?
>
> Joe
>
> --
> ---------------------------------------------------------------------------
> Joe Lumbley(jlumbley@netcom.com)
> ---------------------------------------------------------------------------
--
********************************************************************
* Jacques P. Renaut "I'd dazzle you with brilliance *
* Informix Advanced Support if I only had the knack..." *
* email: jrenaut@informix.com #include <disclamier.h> *
********************************************************************