Re: Newbie Question on Partitions

If your archive partition will not be changed after it's archived, having the archive and the current production partitions in the same tablespace will not allow you to mark those archive partitions read-only via the tablespace. You can put all partitions in the same tablespace, it would be more of a question of should I put them in the same tablespace based off of your system and installation.

HTH,
Pete's

"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 - 08:26:54 CST