Re: partions in Oracle 8

I haven't experimented with the partitioning yet, but I do know that sometimes the optimizer has some difficulty choosing indexes on tables in a view with UNION ALL statements. Keep in mind that with partitions, you can't perform an update that would cause a row to migrate to a different partition. Other than that, partitions look like the best answer. Don't forget that you can also partition indexes.

Good luck,
Dave

John Bishop wrote in message <35048798.FFC70460_at_atl.mediaone.net>...
>I have a conifguration that really lends itself to either using either a
>series of unions with multiple tables, or implimenting partitions in
>Oracle 8.
>
>Has anyone had any good or bad experiences with partitions?
>
>The partitioning gig looks like a great idea - we'll be storing data on
>a monthly basis and the sum of the partions will be the year to date
>table. In other words, I'm looking at creating a partition of 1/1/98,
>2/1/98, 3/1/98... data
>
>OR
>
>I'm creating a table that pretty much has =< N-2 months worth of data
>with month N-1 and month N seperate. (I'm seperating them because they
>will be the most recent, and as the most recent tables N-1 and N tables
>will see the most activity.) So a union would be of N-2(archive) and
>N-1(last month) and N (this month). Moving the data around will be a
>month end process.
>
>So what are your suggestions. The partions look easier to manager, but
>the view lends itself to simplicty (other than the moving around) and
>it's proven technology.
>
>Good or bad experiences are appreciated.
>
>JB
>
Received on Mon Mar 09 1998 - 00:00:00 CST