|
Howard, If you are dropping the indexes before hand (and assuming there aren't any RI constraints on the file), I don't think your sql is having a problem with the 'insert' part. It must be with the 'select' part. Is it complicated? Does the selected file(s) have a lot of deleted records? are you doing an 'order by'? Joins? Also, if I were in ops where you work, I would have booted you out of jail (or thrown you in jail) days before monday... :) Rick ----original message-------- Bruce, I attempted using the DELETE but it just took too long! In the CL I have a RUNSQLSTM that drops the indexes and another to rebuild them at the end. I just can not figure out why the INSERTs went south after the CLRPFM, the program was running fine but it was doing about 1 row every 3 or seconds, ran from the 26th till Monday. What is really surprising is that ops gave me a get outa jail free card on that! :-)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.