Zhu Chao,
You are right to say that with a heap organized table you also have the index to
encumber the SGA and indeed you are right to say that, as I put it, what I said is not
totally correct. I should have been more specific.
The reference to _partitioned_ IOTs implicitly associated them
Zhu/SF:
Thanks for your insight. I was under the impression that Oracle did not
recommend IOT for tables that where not fairly static.
Would the reasoning for this not being an issue in this case be due to
oracle now having to only maintain the IOT table blocks instead of the table
blocks and
Jay,
On the paper, your table is indeed a good candidate for an IOT - it will save you
the space used by the table (you will only have the primary key index). However, there
may be gotchas. I have noticed in the past that IOTs, being primarily indices, have a
tendency to be a bit 'sticky'
Hi, Jay:
Since your table is just a table with 1M records and you have only three
columns(all of them are pk), so using IOT is really an good candicate.
The space save is not important because 1M records with three columns typically
consumes several megabytes, which is not important at
