Re: select/delete on IOT becomes slower as more rows get deleted

I have noted in the past that it appears that Oracle will take longer to
traverse deleted rows in an index scan than non-deleted.  I never went to
the trouble of trying to explain why, but when I worked on a database that
did a large number of index range scans, we observed that rebuilding indexes
when they hit somewhere between 5 and 10% deletes resulted in improved
performance.


On Wed, Feb 4, 2009 at 4:07 AM, Ian Cary <ian.cary@xxxxxxxxxxxxxx> wrote:

>


-- 
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'

Other related posts: