Re: BLOB/CLOB or Organization Index advice

Alf wrote:

> Hi,
>
> Currently I have a table set up as Organization Index. Three variables
> define the index to the parent and four numeric variables are the row data
> (1 to 4 completed).
>
> On average I have 25 rows but at an extreme I could have well over 100.
>
> My database is PC based and with just over a months worth of data I have
> 2635053 rows of detail data for 98950 parent rows - and I intend to have
> many months on-line - though they will be accessed through other tables so
> it can be split between many tablespaces segregated by time (although I
> haven't really though about that yet).
>
> Also, for my application, it generally only makes sense to access the detail
> rows via the parent and access is mainly for reports so fast real-time
> access is not really a priority.
>
> So, finally, my question: is organization index the "best" way to go about
> storing this data given the above?
>
> Are there overheads or limitations implied that I may hit as the amout of
> data grows?
>
> Or, would I be best served packing the data into a BLOB/CLOB field in the
> parent table and parsing out the data into its individual rows as needed on
> query?
>
> Thanks for any input/advice.

I'd be thinking range partitioning using Enterprise Edition.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)