[progress Communities] [progress Openedge Abl] Forum Post: Re: 11.5.1 For Each Table-scan:...

  • Thread starter Thread starter ChUIMonster
  • Start date Start date
Status
Not open for further replies.
C

ChUIMonster

Guest
New problem... new thread? In any event... yes, your DELETE code will be slow if you do it like that. "Chunking" multiple operations into a larger transaction is good for CREATE and UPDATE. It is bad for DELETE and irrelevant for READ. The best DELETE performance is a single thread with one DELETE per transaction.

Continue reading...
 
Status
Not open for further replies.
Back
Top