Application Development 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: 

which one is better

Former Member
0 Kudos

hi

which one is better FOR ALL ENTRIES OR JOINS?

on different occations like more data and etc....

1 ACCEPTED SOLUTION

former_member188685
Active Contributor
0 Kudos

Hi,

it really depends on the situation. some time there is no difference at all. some times Joins performance better than for all entries. some times For all entries is Better than Joins.

Measure the Perfromance and use accordingly.

Regards

vijay

6 REPLIES 6

former_member181966
Active Contributor
0 Kudos

-FOR ALL ENTRIES

Its fast then joins .... just fill up data in internal tables and loop around it .

<b>Check links</b>

http://blogs.ittoolbox.com/sap/db2/archives/for-all-entries-vs-db2-join-8912?sp=CM

http://www.thespot4sap.com/articles/SAPABAPPerformanceTuning_ForAllEntries.asp

http://web.mit.edu/ist/org/admincomputing/dev/abap_review_check_list.htm

http://www.sapgenie.com/abap/performance.htm

Hope this’ll give you idea!!

<b>P.S award the points.</b>

Good luck

Thanks

Saquib Khan

"Some are wise and some are otherwise"

former_member181962
Active Contributor
0 Kudos

Discussed in detail

Former Member
0 Kudos

Depends on the situation. Try both and see. That's what I'd do.

In this , I wrote a program that compared joins over multiple tables against FOR ALL ENTRIES.

Rob

Message was edited by: Rob Burbank

former_member188685
Active Contributor
0 Kudos

Hi,

it really depends on the situation. some time there is no difference at all. some times Joins performance better than for all entries. some times For all entries is Better than Joins.

Measure the Perfromance and use accordingly.

Regards

vijay

Former Member
0 Kudos

Hello Kiran,

It is always prefered to use joins over For all Entry.

If you have less number of records( Around 100-200 records)in internal table then you can use For all entries..otherwise it is better to use joins...

Again do not try to join large number of tables..which will degrade the performance.

You can cross check performance using transaction PA30. Click on Tips and Tricks and you can put both queries simultaneously and measure output performance.

Cheers,

Nilesh

Former Member
0 Kudos

Hi Kiran,

As per the above replies it depends on the situation in which you are going to write your <b>SELECT</b> statements. One thing I can add is that one should be perfect in SQL statements if <b>Joins</b> are to be used.

While <b>FOR ALL ENTRIES</b> is easy to code.

You can use the Transaction <b>SM30</b> to check the performance.

Regards,

Arun Sambargi.