In my first post on Automatic Indexing on Partitioned Tables, I discussed how Automatic Indexing (AI) can now create a Non-Partitioned index if deemed the most effective indexing structure (this wasn’t supported when AI was initially released). A Non-Partitioned index is indeed likely the most efficient indexing structure if the underlying table has many partitions […]
In today’s video we’ll discuss read-only partitions and subpartitions, introduced in Oracle 12.2.
This is based on the following article.
You might find these useful too.
This post is part of a series about the partitioning of database objects.
I have written previously about partitioning the PS_LEDGER table in Financials for the benefit of General Ledger (GL) reporting. I have always recommended top-level range partitioning on the combination of FISCAL_YEAR and ACCOUNTING_PERIOD with separate partitions for each accounting period. It also leaves sub-partitioning available to use another column, usually LEDGER.
However, recent research into partition change tracking (PCT) and materialized views has made me question that advice. The decision is not as clear cut.
This post is part of a series about the partitioning of database objects.
This post is part of a series about the partitioning of database objects.
This post is part of a series about the partitioning of database objects.
This post is part of a series about the partitioning of database objects.
This post is the first in a series about the partitioning of database objects.
Recent comments
3 years 5 weeks ago
3 years 17 weeks ago
3 years 21 weeks ago
3 years 22 weeks ago
3 years 27 weeks ago
3 years 48 weeks ago
4 years 16 weeks ago
4 years 46 weeks ago
5 years 30 weeks ago
5 years 30 weeks ago