Partitioned Tables   «Prev 

Partitioning is the Foundation for Information Lifecycle Management

Information Lifecycle Management (ILM) is a set of processes and policies for managing data throughout its useful life. One important component of an ILM strategy is determining the most appropriate and cost-effective medium for storing data at any point during its life time:
  1. newer data used in day-to-day operations is stored on the fastest, most highly-available storage tier,
  2. while older data which is accessed infrequently may be stored on a less-expensive and less-performant storage tier.
Older data may also be updated less frequently in which case it makes sense to compress and store the data as read-only.
Oracle Database provides the ideal environment for implementing your ILM solution. Oracle supports multiple storage tiers, and since all of the data remains in the Oracle database, the use of multiple storage tiers is completely transparent to the application and the data continues to be completely secure. Partitioning provides the fundamental technology that enables data in tables to be stored in different partitions.
Although multiple storage tiers and sophisticated ILM policies are most often found in enterprise-level systems, most companies and most databases need some degree of information lifecycle management. The most basic of ILM operations, archiving older data and purging or removing that data from the database, can be orders of magnitude faster when using partitioning.

Advantages of Oracle Partitioning

1) A table can be divided into multiple partitions

2) A select statement can be executed against the complete table.

3) The Oracle database will only access the partition (or partitions) that contain data as specified by the WHERE clause of the query

4) Backup and recovery operations can be executed against individual partitions

5) Backup and recovery operations can be executed against individual partitions.
This reduces the overall time needed for these operations

6) If the partitions are stored in different tablespaces, one partition can become unavailable.

While the other partitions remain available.