|
------------------------------
message: 6
date: Thu, 29 Nov 2007 07:31:06 -0500
from: "Wilt, Charles" <WiltC@xxxxxxxxxx>
subject: RE: Improving SQL Update perfomance
Luis,
There doesn't appear to be a where clause on the
statement.
Thus, you're intending to change every row correct?
Any triggers or constraints on these files? Those would
slow you down considerably.
Are the files journaled? If so, make sure you run the
update under commitment control. Or stop
journaling while you run the update.
I wonder if it'd be any quicker to create a temporary
file with the new values then do a CPYF
MBROPT(*REPLACE) back to the original?
HTH,
Charles
-----Original Message-----Luis Rodriguez
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Sent: Wednesday, November 28, 2007 2:42 PMof
To: Midrange-L
Subject: Improving SQL Update perfomance
Hi list,
What would be the best way to improve the performance
a SQL Update statement executed with RUNSQLSTM?
I need to run the following SQL for several tables:
UPDATE LIBNAME/TABLE SET
Field1 = round(field1 / 1000, 2),
Field2 = round(field2 / 1000, 2),
...
Fieldn = round(fieldn / 1000, 2);
Each one of these tables can have several thousands of
records. One of them has 15 million of records, and the
process is VERY slow.
Thanks in advance,
Luis
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.