Oracle partitioning principles

1. Table size: when the table size exceeds 2 GB, or when the table record size exceeds 10 million for the OLTP system, you should consider partitioning the table.
2. Data Access: Most query applications based on tables only access a small amount of data in the table. For such a table, you can make full use of the features of partition exclusion irrelevant data query.
3. Data Maintenance: Batch Data is deleted by time period. partitions are required for such tables to meet maintenance requirements.
4. data backup and recovery: Create a ing between partitions and tablespaces during tablespace backup by time period.
5. read-only data: if most data in a table is read-only, the read-only data can be stored in the read-only tablespace by partitioning the table, which is advantageous for data backup.
6. OLAP parallel data operations