Re: Capacity planning for VERY large table

It is possible to have local bitmap indexes on partitioned tables. But I'm not sure this helps you, what would you partition on ?

Perhaps something like 16 range partitions on F01 with 16 composite partitions on F02, or 32/8.

How can you keep the last 10% of the data when you don't appear to have an 'age value' in the description, and when the data is 'static' ?

--

Jonathan Lewis
Yet another Oracle-related web site:  http://www.jlcomp.demon.co.uk

Michael Bialik wrote in message <8qr0q3$d39$1_at_nnrp1.deja.com>...


>Thanx for responding.

>

> Here are the answers for your questions:

>

> 1. Do all 25 columns always appear in all queries ?

>    -- Yes.

> 2. Do the typical ranges for each predicate cover about 20 values ?

>    -- It ALWAYS cover 20 values.

> 3. Are the values 0..255 used fairly evenly in any given column ?

>    -- Yes again. It is safe to assume that the values have an

>       even dispersion for each column.

> 4. Is the distribution of values in a column highly clustered, or very

>    scattered ?

>    -- My "educated guess" - the values ARE clustered.

> 5. Is this very static data so that it can be bitmap indexed ?

>    -- The data is static, so I thought about using bitmap indexes

>       already. There is ( of course ) a problem that it is NOT

>       possible to use bitmap indexes for partitioned table, so I'm

>       checking the possibility to define 256 table and generate

>       dynamic SQL to perform an UNION of 20 such tables ( for the

>       first column ).

>       All other indexes will be bitmap.

>

>  I'm trying to convince the application designers to keep only last

>  10% of data ( may be even less ). Still the data volumes are going to

>  be impressive.