Table Design With Many Partitions
I'm doing some performance testing on a new schema design I am trying out that is essentially a really wide sparse table. I would like to be able to quickly delete sections of this table so I would naturally lean towards partitions to get this done and issuing a "DROP_PARITION" call when needed.
However, I noticed something in the system limits page that says a table can have no more than 1024 partitions but to keep it aroun 10-20 for good performance. I am wondering if anyone knows if this is a soft limit that could potentially be increased, and if so, what could the potential performance implications be of having potentially millions of partitions?
Any input is appreicated. Thank you.