topic Commit work v/s Update task - Performance impact in Application Development and Automation Discussions

Commit work v/s Update task - Performance impact

Former Member — Tue, 06 Apr 2010 07:26:40 GMT

Hi,

I need to update large amount of data into a ztable using INSERT statement.

This task is performance critical.

Which method of table update will have positive impact on the performance -> commit work or call func. in update task.

Thanks for the help.

regards

Karen

Re: Commit work v/s Update task - Performance impact

Former Member — Tue, 06 Apr 2010 13:45:20 GMT

the update task is for transactional changes of objects (small number), it creates an overhead which is however necesary to insure data consistency.

If you plan to update really a lot of data, then you should work directly with commit works after around 10.000 records.

You must ensure that nobody works in parallel on your updated inconsistent data.

Siegfried

Re: Commit work v/s Update task - Performance impact

Former Member — Wed, 07 Apr 2010 12:01:15 GMT

If you are updating data based on the outcome of some standard functionality, then use "update task" method. Example is updating the Z table from the Sales order User Exit "MV45AFZZ - USEREXIT_SAVE_DOCUMENT" (Update the ztable only if sales order save is successful) . Otherwise use Direct update and commit work.

Regards

Vinod