RE: Runtime for deleteing lots of records -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Jim, doesn't the 400 also balance the index tree from time to time? If it's smart enough only to remove entries in the index for deleted records, eventually the tree could get severely skewed, I would think, and require balancing.

Vern

At 12:52 PM 2/10/03 -0600, you wrote:

I've also heard and observed that extreme database operations can cause
indexes to be automatically rebuilt.  A few years back we were running a
software package conversion that required tables to be dumped to a temporary
area then copied back using CPYF MBROPT(*REPLACE).  We accidentally ran it
without taking the option to drop all the logical files.  We saw that every
hour or so the i/o would freeze and the LF's would take a long hit.

If this is still true in the V5 world and if it applies to deletes you may
have rebuilt your logical files a few extra time during the process.

btw, this is one of the things that drives me crazy about Oracle.  If you're
performing a lot of deletes (like, for instance, if you happen to be running
ANY transaction-based BUSINESS on your database) the indexes will grow
inefficient and require frequent rebuilds.

-Jim

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.