Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Best performance

Former Member
0 Likes
989

Hi All,       I have a performance issue with select query where i am using for all entries.       Is performance improved if i convert that for all entries into ranges table ? Regards, Praveen

Hi All,       I have a performance issue with select query where i am using for all entries.       Is performance improved if i convert that for all entries into ranges table ? Regards, Praveen

6 REPLIES 6
Read only

SharathYaralkattimath
Contributor
0 Likes
961

Not required, just check the for all entries table is not initial.

for filling the ranges, you need to loop the table & fill the range, this will increase program execution  time.

Read only

Former Member
0 Likes
961

Hi Praveen,

At some point, it`s same, i think. All the content will convert to 'OR' condition in native sql.

So if this all entires itab is very big, you`d better just select all data from dbtable directly, do not use 'ALL ENTIRES'.

regards,

Archer

Read only

vinodkumar_thangavel
Participant
0 Likes
961

HI,

For performance based if u use FOR ALL ENTRIES it will be good instead of using ranges because the FOR ALL ENTRIES works in the buffering concept .

Regards,

Vinodkumar.

Read only

Former Member
0 Likes
961

Can you please post the select query ? and also let us know the total entries in the table on which for all entries is performed. is initial check present for The table on which for all entries is performed ?

Read only

robson_soares
Participant
0 Likes
961

I suggest some actions with respect to the fields that will be used as key in the FOR ALL ENTRIES table (FAE):

- Ensure that they are not empty;

- Delete the repeated values;

- Sort it out.

And as said before, verify that the FAE table is not empty.

Using intervals is not a good idea because, depending on database system, there may be a limit of rows within the range.

Read only

Former Member
0 Likes
961

hi praveen,

If the internal table has numerous records and there is a lookup then it is better to make it hashed table type.

by making it hashed table performance will sure improve.