Re: Partition by three column values

Jaromir,

All queries will include acct_id for sure. User can query by other columns too but need not to. Also this table is sort of archival table. It pulls data from various databases and consolidate in a single database. I am not planning to make it a fact/dimension model. We dont expect more than 10 accounts and 30 site_id in next three years.

Thanks

Sandeep

On 2/23/06, jaromir nemec <jaromir_at_db-nemec.com> wrote:
> Deepak, Sandeep,
>
>
>
> > As Sandeep had mentioned, all the queries will
> > definitely have acct_id. But he didn't mention whether
> > cr_date will also 'always' be there.
>
>
>
> my point was very simple. By the decision about the partitioning I would
> additionally consider the following:
>
>
>
> if the time dimension (cr_date) consists of a large number of distinct
> values (e.g. timestamps) it is better to assign it as a range partition key.
>
>
>
> if some dimension is used alternatively with BETWEEN predicates it is better
> to assign it as a range partition key. A between predicate could be quit
> common for time dimension.
>
>
>
> But yes of course in special case if the time dimension has a fixed
> granularity (e.g. monthly) and you get one new account per month on average,
> there is no really a big difference between those two dimensions.
>
>
>
> Regards,
>
>
>
> Jaromir
>
>
>
>
>
> ----- Original Message -----
> From: "Deepak Sharma" <sharmakdeep_oracle_at_yahoo.com>
> To: <jaromir_at_db-nemec.com>; <dubey.sandeep_at_gmail.com>
> Cc: <oracle-l_at_freelists.org>
> Sent: Thursday, February 23, 2006 5:09 AM
> Subject: Re: Partition by three column values
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
http://www.freelists.org/webpage/oracle-l