RE: IOT Vs Normal Tables

FYI, this statement is no longer true, at least not in 8.1.6.

"Currently, Oracle8 doesn't let you create

   additional indexes against an index-organized table."

I use IOT's quite a bit (because the app is very space conscious) but I'm thinking of getting rid of them if the export/import doesn't work. I guess I'll have to look into that...

-----Original Message-----
From: Eric D. Pierce [mailto:PierceED_at_csus.edu] Sent: Friday, December 15, 2000 2:32 PM
To: Multiple recipients of list ORACLE-L Subject: Re: IOT Vs Normal Tables

As usual, feeling like an idIOT for not knowing what "IOT" even means(!, actually, forgetting), I web searched, and found this stuff:

("Extensible Indexing - What is it and who needs it?":) http://technet.oracle.com/products/oracle8i/htdocs/ext.htm (author, Srikant Sarda mailto:srsarda_at_us.oracle.com )

-
http://technet.oracle.com/products/oracle8i/htdocs/ext.htm

---
excerpt:

   Identify the tables you can index-organize. Index-organized
   tables are easy to implement. They save space and reduce the
   number of I/Os necessary, because all table data is stored in
   the index structure. Currently, Oracle8 doesn't let you create
   additional indexes against an index-organized table. When
   identifying candidates, look for tables with only one index.
   Tables that have the most to gain from being index-organized
   are those where most of the data is already stored in the index
   (providing maximum space savings), where few changes
   occur to the table (this would cause index fragmentation), and
   cases in which the table is almost always accessed through
   the index. Reference tables often have these characteristics.