Best practice in table fields update (big table)

jepi_flanders — Thu, 28 May 2020 07:45:49 GMT

Hi everybody,

I'm wondering which best practice shall be adopted in the following scenario:

ECC 6.0 (SAP_ABA 700)

Oracle 12.1.0.2.0

Z table with 53 fields, 3 fields as primary key (plus 1 for MANDT), total fields length 831 Bytes
the table contains more than 13 mil records;
out of them, about 350 k shall have two fields that need to be changed (with different values per record)

While looping through the records finding those to change, and calculating the two fields new values to modify, shall I go with UPDATE... SET... WHERE?

Or, shall I collect the records and do an UPDATE... FROM TABLE...? (in such a case, how many records shall I process? one shot?)

When to do a Commit Work?

Any suggestion on this is highly appreciated!

Thank you and Kind regards,

JFlanderds

Re: Best practice in table fields update (big table)

chaitanya285 — Fri, 29 May 2020 12:25:33 GMT

Hi,

go to ABAPDOCU t code and search for INSERT, UPDATE and MODIFY keywords. There you will get the exact use and syntax of these statements while inserting or updating records in database table.

Now, for your question, it is always recommended to perform operations on data, store that data in internal table and then modify database table from that internal table in one go. This is minimize the actual database access.

Please search on SCN for any question before adding new question as some similar questions might be anweserd already 🙂

topic Best practice in table fields update (big table) in Application Development and Automation Discussions

Best practice in table fields update (big table)

Re: Best practice in table fields update (big table)