Creating Indexes on partitioned tables

[@Firatayrilik]

Do indexes make queries on partitioned tables even faster? For example, for the index on "customer" column in this video, for which type of queries does the index become more efficient?

[@DatabaseDude]

Maybe faster...maybe slower. The same rules apply - namely, do we reduce the amount of IO, and does the benefit outweigh the cost of keeping that index up to date.

[@alessioruggi9676]

I want to ask something that could seems trivial, but i can't find online nothing that txplains it well. Why status for partitioned index is "N/A"? i've been able only yo find this definition "N/A indicates that index is a partitioned index, not applicable for User_indexes and dba_indexes need to view with user_ind_partitions and dba_ind_partitions." I can't really get what the part after the comma means, and also what the N/A stands for?

[@DatabaseDude]

N/A means the status is determined at a lower level. For example, if you have 8 partitions in an index, and 3 are "unusable" and 5 are "usable", then you really can't make a statement about the overall status of the index, hence "N/A"

[@alessioruggi9676]

@@DatabaseDude thanks a lot!

[@SudhirBhajnawale]

Very well explained. Thanks

[@giorgio89458]

Hello! what happens if I add the clause "UPDATE INDEXES" even if I drop a partition with a local partitioned index? will it give me some errors?

[@DatabaseDude]

it will work fine

[@carolinestone1977]

xcjek vun.fyi