Re: Newbie Question on Partitions

There is no such requirement that partitions should be placed in different tablespaces. Though it may help sometime by distributing IO.

I certainly hope that you are not trying to partition the production table by the archive flag, which seems to be what you were suggesting. Updating the partition key will cause physical row movement which I would try to avoid. It is best that you build the partition key so that when a new record is created it already knows which partition it belongs and move into that partition automatically.

• Jusung Yang

"M2" <me_at_quietplaceiwithnospam.com> wrote in message news:<ke_3a.65$Aq3.12506_at_news.optus.net.au>...
> Hi,
> just a quick newbie question on partitions. I have a very large table (40
> million rows) that I want to move into partitions. The plan here is to
> create two partitions one for "archive" rows and the other for production
> rows. I will then periodically update rows to set the archive flag (causing
> a change in partition) and move the data off to a warehouse. The partition
> will then be dropped to recover the space.
>
> So, my question is, will this be efficient if both the archive and
> production partitions are in the same tablespace? Everything I read seems to
> mention partitions synonymously with different tablespaces but is it
> possible to do it in the same space? What would I lose out on?
>
> Matt.
Received on Mon Feb 17 2003 - 12:37:06 CST