topic Re: Abap performance in Application Development and Automation Discussions

Abap performance

Former Member — Mon, 02 Oct 2006 00:31:35 GMT

HI ALl ,

In My program , i got one internal table (itab) and one

customized database table say DB

I fill itab and then deletes the existing records in table DB and now i have to fill DB with records in table

itab .

I have two optins :

LOOP AT ITAB. modify db from itab . Endloop .

MODIFY DB FROM TABLE ITAB .

which one is better(performace wise) and should i write commit work after

these statements .

Thanks in Advance .

Re: Abap performance

gopi_narendra — Mon, 02 Oct 2006 00:40:12 GMT

u can just use the modify statement and no need to write any commit after that

modify ZTABLE from table ITAB.

**make sure the internal table ITAB is of type ZTABLE**

PLEASE CLOSE ALL THE PREVIOUS THREADS IF PROBLEM SOLVED

Regards

Gopi

Message was edited by: Gopi Narendra

Re: Abap performance

former_member186741 — Mon, 02 Oct 2006 01:01:55 GMT

I believe the 2nd option (from table) is better and that no commit is required. An implicit commit will occur when your program ends..... of course if you have a complex program you may need to put one in but for normal purposes it's not needed.

If your table is small or medium the performance benefits may be small so if you wanted to, say, catch errors and show them on a report for update failures then the first option would be ok.

Re: Abap performance

Former Member — Mon, 02 Oct 2006 01:22:34 GMT

Hi,

The second option is better performance wise. No need to write COMMIT WORK .

Best regards,

Prashant

Re: Abap performance

Former Member — Mon, 02 Oct 2006 08:36:12 GMT

Hello,

Go for,

MODIFY DB FROM TABLE ITAB .

Because, if the internal table entries are not in DB then the DB will be inserted with those table entries, Otherwise, the record will be modified against internal table.

Performance is also good because, you are accessing the DB at once and not in loop.

Regs,

Venkat

Message was edited by: Venkat Ramanan Natarajan

Re: Abap performance

Former Member — Mon, 02 Oct 2006 08:49:50 GMT

hi,

Most of the performance issues are related to database. It should be an inherent practice to reduce the access to database as far as possible and use it in the most optimal manner.

Just as in select statements, database updates also affect the performance. When records are to be inserted in database table do it in once. Populate the internal table completely, with which the records are to be inserted. Then update the table from the internal table instead of updating it for each record within the loop.

Do not use

	Loop at i_mara.
		---------------
		---------------
		mara = i_mara.
Modify mara.
	Endloop.

Avoid accessing database multiple times even for updating the records.

As is seen the table mara is modified for each record. The performance can be considerably improved if the internal table is populated and then the table is updated once for all the records.

Instead use the statement

Loop at i_mara.
--------------
---------------	
Modify i_mara.
Endloop.

Modify mara from table i_mara.

As is seen the table mara is modified for once in the end. The performance is considerably improved and the database access is reduced.

Regards,

Sailaja.

Re: Abap performance

Former Member — Mon, 02 Oct 2006 10:11:33 GMT

Hi,

1) modify db from table itab will be better for

performance wise because database will be accessed

once per all table entries where as in

loop at itab.

endloop.

database is hit for each record and it may take

time because of network activity .

use option 1 and use commit work after modify statement

so the changes are reflected in database

Regards

amole

Re: Abap performance

Former Member — Wed, 04 Oct 2006 08:40:38 GMT

Hi ,

modify db from table itab will be better for

performance wise because database will be accessed

once per all table entries where as in

loop at itab.

endloop.

database is hit for each record and it makes performance poor.

use modify db from table ...

need not use commit work...also no prob if u use commit work/

if u use commit work..the modification is reflected immediately in the table..as the execution is passed through the commit statement.

if u dont use ...then it reflected to table only at the end of execution of program,.

Regards,

Ajith

Re: Abap performance

anversha_s — Wed, 04 Oct 2006 08:40:43 GMT

hi,

dont write the select or othere data base queries inside the loop.

it will affect the performace badly.

so use MODIFY DB FROM TABLE ITAB .

rgds

anver

pls mark all hlpful anwers