Hi,
Could anybody briefly explain, what needs to be done in order to make a table partitioned?
I will not actually do the changes, so no details are needed. I only need to understand the consequences...
We have a few very big tables with data from last 3 years. We would like to create partitions for each year (total of 5 years - legal restrictions). Only the latest data should reside on a fast device. The other four partitions should be on something slow, maybe a tape.
I already know, that we have to re-create the table.
What about the indexes? Shall we change them or not? Based on what should we decide? And what about primary keys?
We use RULE optimization. Is this a problem?
We cannot change hints used when application generates queries, we only can add another "where" condition. Will it be enough?
Thanks a lot.
Could anybody briefly explain, what needs to be done in order to make a table partitioned?
I will not actually do the changes, so no details are needed. I only need to understand the consequences...
We have a few very big tables with data from last 3 years. We would like to create partitions for each year (total of 5 years - legal restrictions). Only the latest data should reside on a fast device. The other four partitions should be on something slow, maybe a tape.
I already know, that we have to re-create the table.
What about the indexes? Shall we change them or not? Based on what should we decide? And what about primary keys?
We use RULE optimization. Is this a problem?
We cannot change hints used when application generates queries, we only can add another "where" condition. Will it be enough?
Thanks a lot.