Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from lizard_rgm on Jun 30 at 8:16 PM first off, commit work does not update any tables, it just removes the rollback log.
after this log is removed, transactions that read the db (with all the updates), do not have to revert to the old (pre) version that was in the rollback log (as its gone).
the thing to remember is that updates to tables happen immediately at the DB level, and commit work makes the change permanent and its effect felt by other luw(s).
the "and wait", will actually slow full down as the v2 updates will also need to finish prior to the records being removed from the log.
as a general rule, you should never use "and wait", and you should rarely use commit work.
commit work should only be used to reduce the size of the rollback log where a massive update is expected or to get around bad system settings.
the other exception is where you are using code that only executes on commit work - such as BAPIs. in that case you must use the bapi commit work.
Regards, Ralph McKnight
| | | ---------------Original Message---------------
From: R. N. Wilhite
Sent: Thursday, June 28, 2012 10:57 AM
Subject: SAP Buffering Table
That is one of the things I was remembering. The other I will have to
research further.
Neal |
| Reply to this email to post your response. __.____._ |   _.____.__ |
