Re: index organized tables

Well ...
  you should have one index for every entry path into your   table.

  You should have constraints for every bussiness rule that   applies. The mandatory bussiness rule is for the   Primary Key ... which columns identify your object ?

  When you say, the event can occur multiple times, but each   time the information can be different to you mean:    the information can be different, or does it have to be    different.

  For the later it would mean that you would have to create   an unique index over event and information.

  If you will be searching by shippingid and eventcode and timestamp   you have to consider:
    Do you always search with all three columns ?     If not ... you will need three seperate index, if      yes ... you can but them in one index

  you argument for the bitmap index is faulty ... be aware that   you should only use bitmap index in environment where the data   is more or less stable (few datachanges), otherwise the   performance will suck you down.
  And what do you want to have an index on eventcode anyway ?

  Index Organized Table: An index organized table is a table that     exists only within the (primary key index). This means that     you will have to include all columns in your index and     specify the table explicit as index organized.     Warning: in 8.0.x you can have only one index on an IOT.      in 8.1.x you can have more

Regards
Dante

    only one index on an

In article <7h1qe2$nmu$1_at_nnrp1.deja.com>,   usmrall <srallapally_at_netscape.net> wrote:
> Hello all,
> I have a table containing a shippingid,eventrank,eventsuffix,placeofentry,
> eventcode,timestamp,information. Now, in the OLTP system, the same event
> can occur multiple number of times, but each time the information
> can be different. As a result the only way to have a key is to make a
> composite key of all the fields. I have a few questions.
> Does this approcach make sense ?
> Doesn't this result in an index organized table and is that good or
> bad,performance-wise ?
> I will be searching this table by shippingid and eventcode and timestamp.
> Assuming no need for referential integrity, how will my performance
> be affected if i had two indexes:
> a. an index on shippingid,eventcode,date (in that order)
> b. a bitmap on eventcode (since the unique values of eventcode are very
> small( < 50) compared to the number of rows in the table (a mil. plus))
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Sat May 08 1999 - 13:44:35 CDT