Implicit Partitioning in Oracle
I am designing a new laboratory database.

Each of my primary data tables will have at least a _`table`_`_id *PK (NUMBER)` and `created_on (DATE)`.  Both columns will increase together, so in other words, a higher `table_id` will have a later `created_on` date.

As in most cases, recent data will be accessed most frequently, so to increase performance, I plan to partition by `created_on`.  Obviously to take advantage of the partitioning, any queries on the tables should filter by `created_on`.

Since both columns increase together, the table is implicitly partitioned by range on `table_id` also.  How can I take advantage of the implicit partitioning by range to increase performance on `table_id` for table joins?
Implicit Partitioning in Oracle
===

I am designing a new laboratory database.

Each of my primary data tables will have at least a _`table`_`_id *PK (NUMBER)` and `created_on (DATE)`.  Both columns will increase together, so in other words, a higher `table_id` will have a later `created_on` date.

As in most cases, recent data will be accessed most frequently, so to increase performance, I plan to partition by `created_on`.  Obviously to take advantage of the partitioning, any queries on the tables should filter by `created_on`.

Since both columns increase together, the table is implicitly partitioned by range on `table_id` also.  How can I take advantage of the implicit partitioning by range to increase performance on `table_id` for table joins?