Search This Blog

Monday, February 1, 2010

One way for Avoiding SQLEXEC usuage

How to mitigate the performance issues because of using a sqlexec while coding? the simple answer is avoid using it.

Consider we have an sqlexec which will be executed in a loop several times, as shown in the first screenshot. Using stanalone rowset/record creation can solve this problem to an extent.

The second screen shot shows a simple way to replace the first sqlexec statement. It wont look great, but it can contribute towards the performance of your applicantion.


1 comment:

  1. Hi

    I tried this out in a test, running the same query 10,000 times again and again with the same input (this means that oracle took almost no time to give the response because the data would be cached in the buffer pool).

    For me, it takes 20 seconds for the sqlexecs to complete and it takes 40 seconds for the rowset fills to complete