Thanks for the question, Panagiotis.
Asked: March 05, 2026 - 1:16 pm UTC
Last updated: March 05, 2026 - 11:56 pm UTC
Version: 23ai
You Asked
Well hello i just wanted to ask you when you have 100000000 rows of data and the best partitioning strategy is to use partition by range with subpartition by hash (having a column that is date type called hired and in the range we have YEAR(hired) and in the hash we have MONTH(hired)) how we will know the number of the partitions we will have to create in the table so we can have the best performance when we query data? thanks.If you don't understand my question i can provide the code if you ask me thanks.
and Connor said...
Providing the code will help, but if you have a *date* column called HIRED I would simply range partition on that column. If you want month granularity, then partition by range. I don't see a need for the two-level partitioning.
Obviously the entire topic of *if* you should partition, and *what* you should partition on, is not really a database question but a business requirements question