|
|
|
|
|
|
|
|
| Re: How to identify table need resequencing. [message #433632 is a reply to message #433623] |
Thu, 03 December 2009 06:07  |
JRowbottom
Messages: 5933
Registered: June 2006
Location: Sunny North Yorkshire, ho...
|
Senior Member |
|
|
I would say that a table never NEEDS 'resequencing'
If you had a table that was mainly accessed by queries using the same access method (eg index range scans on the same index) and you didn't mind the fact that what you were going to do would adversely affect all other access paths then you could do what you're saying.
To see if it needs doing, have a look at the CLUSTERING_FACTOR on the index that you want to order the table by.
As Tom Kyte explains here if the clustering_factor is near to the number of blocks in the table, then your table reflects the order of that index. If the clustering factor is near the number of rows in the table, then the table is randomly ordered with regards to this index.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
