Hello all!
I created a range-partitioned table, and noticed that indexes were created
as "NOT PARTITIONED" (through db2look), even though I ran the index creating
commands without this parameter.
Not that I care too much now about it :-)
But what will happen when once upon a time in the future I execute the
"attach partition" command, and so add another partition to the existing
(partitioned) table.
Will the indexes then be automatically rebuilt, or do I have to do it myself
(perhaps by executing the "set integrity" command), or else...?
Another question: can I at all have a partitioned table where each table
partition has its own "index-partition", and does this make any sense at all
(why partition the index) and in what way (performance improvements, ...)?
Regards,
Damir
I created a range-partitioned table, and noticed that indexes were created
as "NOT PARTITIONED" (through db2look), even though I ran the index creating
commands without this parameter.
Not that I care too much now about it :-)
But what will happen when once upon a time in the future I execute the
"attach partition" command, and so add another partition to the existing
(partitioned) table.
Will the indexes then be automatically rebuilt, or do I have to do it myself
(perhaps by executing the "set integrity" command), or else...?
Another question: can I at all have a partitioned table where each table
partition has its own "index-partition", and does this make any sense at all
(why partition the index) and in what way (performance improvements, ...)?
Regards,
Damir