RE: Add/Drop partition and CBO statistics

Sometimes you want to run queries on partitions (using partition pruning or just using tablename partition (...)) and sometimes to run queries on whole tables.

Currently I'm working on project where I have partitioned tables with data to process. First, I run checks on whole tables (to make sure data is valid) and then process partition by partition just to work with smaller blocks of data. So I have global indexes to support validation queries and local indexes to support actual data processing.

rw

> Agreed that scanning one big index is faster than many partitions.
>
> Then raises the questions - I thought partitioning is for:
>
> 1) ease of archiving/dropping off old partitions - drop old
> and create new
> partitions in a sliding window. A single large global index negates a
> lot of this ease - even though it is true that deletes on
> non-partitioned tables
> would be even more inconvenient.
>
> 2) efficiencies in partition pruning for queries. If you are
> "querying whole table" - why bother with partitioning?
>
> The point then becomes you don't need to partition in the
> first place, or
> your partitioning scheme is not appropriate?
>

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Wartiak Rastislav
  INET: RWartiak_at_cpoj.cz

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).