Re: Partition Question (8i)

Then partition the table as you presented and add an index for the alternate access pattern.

BTW, partitioning is more of a data management thing than it is a performance thing. Partitioning gives you more options for inserting and deleting large chunks of data. The textbook example is time series data. You only insert new data. As the data ages, updates become less frequent. Old data becomes irrelevant and needs to be removed.

"Alex Vilner" <alex_at_sinoma.com> wrote in message news:22e9f6e0.0202270614.33fc7a61_at_posting.google.com...
> I should have clarified some more -- the queries are done in any way
> the user wants them :( However, the most common access to data is done
> via EITHER group # or location. They are not used in combination, and
> one does not have a higher frequency of occurrence than the other.
>
>
> "bdick" <bdick_at_cox.net> wrote in message
news:<quOe8.14331$s03.408346_at_news2.east.cox.net>...
> > "Alex Vilner" <alex_at_sinoma.com> wrote in message
> > news:22e9f6e0.0202260702.d47e848_at_posting.google.com...
> >
> >
> > Do you have queries that specify the loc# without the group#? If so, you
can
> > swap the partition columns. Make it group#, loc#?
> >
> > If you have a mix of queries, some specifying only loc# and some
specifying
> > only group#, the partition the table by the most frequently queried
column.
> > Then add a partitioned index to the other column. If your other-column
index
> > is local, then each index partition will be scanned (faster than table
> > partition scan). If your other-column index is global, then only the
> > pertinent index partitions are scanned (faster yet).
> >
> > Global partitioned indexes may provide faster access in some situations,
but
> > are more difficult to maintain than local partitioned indexes. See
chapter
> > 11 Partitioned Tables and Indexes in the Oracle Concepts manual.
Received on Wed Feb 27 2002 - 08:55:10 CST