That is the recommended way. I have a 6 partition table with each partition
in a different tablespace and each table space on a different drive. It's
working well!
Ruth
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Wednesday, September 25, 2002
We currently are creating partitions of a given table in individual
tablespaces (1 partition = one tablespace). To me, this seems like a
reasonable practice. Anyone have any thoughts about this they would like the
share?
RF
Robert G. Freeman - Oracle OCP
Oracle Database Architect
CSX Midtier
That's the way I've done it.
It let's you drop a partition and drop the tablespace
so nothing is left.
--- Freeman, Robert [EMAIL PROTECTED] a
écrit : We currently are creating partitions of a
given
table in individual
tablespaces (1 partition = one tablespace). To me,
this seems like a
it's what I'm planning on doing... seems to me that when we decide to
remove partitions, we can easily do so and retrieve the disk space this
way
--- Freeman, Robert [EMAIL PROTECTED] wrote:
We currently are creating partitions of a given table in individual
tablespaces (1 partition = one
We have a database which stores 5 years data with most
of the tables partitioned on year_month. We have three
tablespces each for each table, with tablespace_1
having 01,04,07,10 months and tablespace_2 having
2,5,8,11 and tablespace_3 having 3,6,9,12
--- Rachel Carmichael [EMAIL PROTECTED]
Another approach is to partition according to your load strategy, but make
them reside in tablespaces according to how you want to set them to READ
ONLY.
For example, if you load daily, partition daily. But if you want to set the
data into READ ONLY to reduce backup volumes on a quarterly
