×
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.
I had to create an (unique) index over the work table before the DELETE performed as it was on V7R3.
The V7R5 upgrade has been very bad for SQL performance.
--
Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of dr2@xxxxxxxx
Sent: Saturday, December 9, 2023 10:09 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Database / SQL performance question...
Greetings,
This week, one of our group had occasion to us SQL to insert a large
number of records into a work file. It was a simple INSERT INTO FROM
WHERE... It went rather quickly.
When he was finished with those records in the work file, he then issues
a simple DELETE FROM WHERE... against his work file. The DELETE took
SUBSTANTIALLY longer than the insert. REUSEDLT isn't an issue and is
off.
It's been a while since I've played in this space, so, I'm curious as to
what, on a MI/DBMS level, is going on that would account for the
substantial time/resource difference.
Thanks
DR2
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.
midrange.com
