You don't ever want to design an architecture where you move rows between
partitions. Try to figure out a way to either partition so that the entire
partition can be exchanged out (or archived).
--
Best of Breed Oracle Tools
* ER Diagramming Tool - DBArtisan
by http://www.embarcadero.com
* PL/SQL Editor - SQL Navigator
by http://www.quest.com
* Database Monitoring - DBFlash for Oracle
by http://www.confio.com
* SQL Tuning/Optimization - DB Expert
by http://www.leccotech.com
"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 Tue Feb 18 2003 - 13:45:01 CST
