Databases Reference
In-Depth Information
F_SALES
partition:
Y11
(values less
than
20120101)
partition:
Y12
(values less
than
20130101)
partition:
Y13
(values less
than
20140101)
tablespace:
p1_tbsp
data file(s):
t1_df1..N
Figure 12-2.
A partitioned table with only one tablespace
This approach has some advantages over a nonpartitioned table, in that you can perform partition maintenance
operations (drop, split, merge, truncate, and so on) on one partition without affecting others, thus ensuring partition
independence. However, the approach doesn't quite take advantage of all that partitioning has to offer.
The next example places each partition in a separate tablespace:
create table f_sales (
sales_amt number
,d_date_id number)
tablespace p1_tbsp
partition by range(d_date_id)(
partition y11 values less than (20120101)
tablespace p1_tbsp
,partition y12 values less than (20130101)
tablespace p2_tbsp
,partition y13 values less than (20140101)
tablespace p3_tbsp);
Now, the data for each partition are physically stored in their own tablespace and corresponding data files
(see Figure
12-3
).
