When long running processes got disrupted, one may not see any expected result.
How to make sure that the result of each operation is saved to disk in a loop?
Regards,
David
Simple: don’t use a database – you’re asking to violate ACID.
A database’s power comes from set-based operations. You’re asking to do single row operations. Use a spreadsheet...or a plain text file and treat it like a log.
Mike
Or commit every loop (perhaps every N loops, depending on how much you're prepared to re-do.)