Re: Index organized table

Epicentre Team B Annecy <carmanet_at_epicentre.fr> wrote:
>Hi Ive,
>
>No, this table is definitively not a good candidate for INDEX ORGANIZED
>TABLE!
>Indeed, indexes severely degrade insert performances, so I let you see with
>an index organized table...

No. It depends on the access pattern, not the insert activity.

An IOT that's heavily inserted into will be more costly than a normal table; but if it's frequently accessed by primary key, with several "nearby" values being pulled out together, then overall IO may still be reduced.

The "sequential number column" as the PK does look suspiciously like that this might not be the case.

>"lve" <lve3162_at_yahoo.com> a écrit dans le message news:
>93096888.0205150620.68aa6cf7_at_posting.google.com...
>> I have a table in an OLTP database which is subject to very frequent
>> inserts. The table has a sequential number column which is the primary
>> key of the tables. Rows are almost never deleted from this table-
>> they are, of course, archived every couple of months.
>>
>> Is this table a good candidate for INDEX ORGANIZED TABLE?
>> I am using oracle 8.1.7

-- 
Andrew Mobbs - http://www.chiark.greenend.org.uk/~andrewm/