Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
ackerbau@us.ibm.com — — source: Informix-list mailing list archive (1991-1998)
Lena --
If you code the delete as a cursor that implicitly deletes one record at a
time, it should not adversely affect logging. The only way you'd fill up
your logs is if you issued a "delete from table where . . ." in dbaccess.
A foreach cursor in SPL should do the trick very nicely for you -- no
explicit commit statements required if you delete a record at a time in the
cursor.
-mka
Michael Ackerbauer
SP Platform Evaluation Test
Systems Verification/Integration Webmaster
Please respond to lena_peltonen@my-deja.com
Sent by: owner-informix-list@iiug.org
To: informix-list@iiug.org
cc:
Subject: How to break up a big transaction?
Hi all,
I'd need perform a huge delete operation
(about million rows). I wouldn't like to add several logs
for this single transaction that will be run very rarely.
So how can I break up a delete operation so that it would do
commit e.g. after every 5000 rows?
I was told that I could use dbloader but is there any way to do it
from SPL or C/ESQL script?
Any help would make me most grateful.
Best Regards
Lena
Sent via Deja.com http://www.deja.com/
Before you buy.
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.