sql - Is PARTITION RANGE ALL in your explain plan bad? -


here's explain plan:

select statement, goal = all_rows   244492 4525870 235345240  sort order   244492 4525870 235345240   **partition range all**   207633 4525870 235345240    index fast full scan mct mct_planned_ct_pk 207633 4525870 235345240 

just wondering if best optimized plan querying huge partitioned tables.

using oracle10g

partition range all means predicates not used perform partition pruning. more info. or, alternative (scanning table blocks instead of using fast full scan on index) estimated more expensive overall.

if can change predicate limit affected rows small subset of partitions, database able skip whole partitions when querying table.


Comments

Popular posts from this blog

ASP.NET/SQL find the element ID and update database -

jquery - appear modal windows bottom -

c++ - Compiling static TagLib 1.6.3 libraries for Windows -