The last blog, here, discussed different single-level partitioning strategies. This blog will explain strategies to make non-partitioned tables partitioned tables. The objects created will be stored in the HR schema. First, a table needs to be created (this is the same table that was created in the last blog) and a unique index will be put on the column CUSTOMER_ID:
Viewing entries tagged
Partitioning tables is a great way to improve the performance and manageability of a table. Sometimes, non-partitioned tables are created that don’t contain much data, but over time the table becomes largely populated. Partitions can be used to manage the proliferation of data in the table. Common single-level partitioning strategies include list partitioning, range partitioning, and hash partitioning. Each partitioning strategy has its own advantages and disadvantages.