Re: Partion Tables

1. Yes, the partitioned table has to contain the column on which the partition is defined

Since this not the answered you wanted for the first question I suspect it makes the other two somewhat meaningless

In general apart from joining two partitioned tables which are partitioned identically the optimiser will not automatically pick the correct partition to join to - if it can infer that only one target partition is relevant it will probe each partition in turn until it finds the right one - but with a lot of partitions this could be expensive.

There are sundry ways to address the
SKU moving across hierarchy problem,
best bet is to refer to one of the classic texts.

--

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

Tim & Mary Seyfried wrote in message ...
>I am a technical lead at Fort James Corperation and building a very large
>Data Warehouse.
>
>I am looking at the possibility of using partioning to improve performance.
>
>I have two tables:
>
>Product Fact_table
>SKU ------------------------------< Sku
>Product_group Fact
>Business_segment
>
>I would like to partition the fact table by business_segment
>
>I have the following questions
>
>1) Does business_segment have to be a field maintained in the fact_table?
>2) Will oracle figure out what partition to go to if my front end product
>express ram formulates the following query:
> select a.product_group,
> sum(fact)
> from product a,
> fact_table b
> where a.product group = 'AAAA'
> group by a.product group
>3) What will need to happen if a sku changes business_segments
>
>
Received on Thu Sep 16 1999 - 07:42:11 CDT