Database Reference
In-Depth Information
ganized table to be divided into smaller pieces. For example, partitions can al-
low you to segregate data based on a date range, where data of one date range
can reside in one partition while that of another will reside elsewhere. From an
application perspective, there is absolutely no difference, as it will view all parti-
tioned and non-partitioned tables identically. But from a database administration
perspective, each of the partitions can be administered as a whole or individu-
ally. This provides the administrator with the ability to maintain different storage
characteristics for each partition, take different partitions offline without affecting
others, and improve DML efficiency.
Taking advantage of database partitions will improve both
console and transactional performance particularly if you
maintain a lot of historical audit data.
From an Oracle SOA Suite
11g
perspective, you might want to consider parti-
tioning your database if you decide to maintain a lot of historical audit data. Par-
titioning is not enabled by default, so this is an activity that must be performed
manually in conjunction with an experienced DBA any time after the product has
been installed.
Converting your non-partitioned Oracle SOA Suite 11g
product tables to partitioned tables is a nontrivial effort, and it
is strongly recommended to involve an experienced DBA.
The following points should be noted when considering the move to partitioned
tables:
