Re: Case for Index Organized table?

From: Ram Raman <veeeraman_at_gmail.com>
Date: Mon, 23 Apr 2007 19:12:39 -0700
Message-ID: <effc058d0704231912r171543bavbe6f18b47b167369@mail.gmail.com>

Thanks everyone for the replies.

The rows are different for everyday, like this:

 for eg:

Jan 01, 2007, 08:01:01am   <--- Row 1
Jan 01, 2007, 08:01:02am   <--  Row 2
Jan 01, 2007, 08:01:03am   <--  Row 3

..
..

On 4/23/07, dbvision_at_iinet.net.au <dbvision_at_iinet.net.au> wrote:
>
> On Tue Apr 24 3:11 , "Ram Raman" sent:
>
> >Hi all,
> >
> >I got a requirement from the developers to build a new table which has a
> column
> that will hold every second of every business day. That is the only column
> in the
> table. The table will be truncated everyday and loaded with the subsequent
> day's
> time. The developers told me that this table speeds up their queries, I
> also
> talked about using other ways but they said that they tested a few ways
> and found
> this one the best. They also want an index on that table. I am thinking of
> creating an index organized table for this purpose. Does anyone foresee
> any
> problem in this approach.
>
>
>
> None at all. But I'm having a lot of trouble
> trying to visualize why a table with a row for every
> second of a business day would need to be reloaded everyday?
> What, different days have different seconds/time durations?
> .
> .
> .
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Mon Apr 23 2007 - 21:12:39 CDT