Re: Case for Index Organized table?
- From: "Stefan Knecht" <knecht.stefan@xxxxxxxxx>
- To: veeeraman@xxxxxxxxx
- Date: Tue, 24 Apr 2007 08:27:27 +0200
I'd certainly, as previously suggested, try to solve this using SQL, not a
table. However, you didn' t give much information as to what you're actually
trying to do. If you absolutely must use a table, also consider using a
single table hash cluster. It might outperform the IOT. But you'd have to
benchmark it in your environment.
Stefan
On 4/24/07, Ram Raman <veeeraman@xxxxxxxxx> wrote:
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@xxxxxxxxxxxx <dbvision@xxxxxxxxxxxx> 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?
> .
> .
> .
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
=========================
Stefan P Knecht
Consultant
Infrastructure Managed Services
Trivadis AG
Europa-Strasse 5
CH-8152 Glattbrugg
Phone +41-44-808 70 20
Fax +41-808 70 12
Mobile +41-79-571 36 27
stefan.knecht@xxxxxxxxxxxx
http://www.trivadis.com
=========================
Other related posts:
