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

difference between for all entries vs innerjoin

former_member223446
Active Participant
0 Likes
2,154

hi dudes

let me know

what is exact difference between for all entries n innerjoin.

what r optimization techniques.

what is performance tunning.

advanced thanks

kiran

5 REPLIES 5
Read only

Former Member
0 Likes
1,752

hi ,

innerjoin : join the two tables when primary key relation is compalsary.at a time join three tables only

forallentries : joining the two tables primary key is not requried but same field existing in two tables.

Read only

Former Member
0 Likes
1,752

Hi,

for performance tuning refer to the below site.

http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_PerformanceAnalysisTools.asp

Regards,

Bindu.

Read only

Former Member
0 Likes
1,752

In Innerjoin Tables are combined at the data base level. In for all entries tables are joined at Application server.

Performance wise for all entries is better than innerjoin if number of tables to join is more than two.

To use for all entries you have to check the first table initial are not. If it is initial then selection will be unlimited. So you have to check it first and then only use it in for all entries.

Read only

Former Member
0 Likes
1,752

The most important difference between a inner join and FOR ALL ENTRIES is that the inner join is performed between two Database Tables. While for all entries is an operation between a Database Table and an Internal Table.

For all entries it is always necessary to check whether the driving table is empty or not.

useful Rewards points*****************

Read only

0 Likes
1,752

hi all,

" Inner join" best sutable for when u are accesing data from data base. but "for all entries" it is best when u are using more than 2 tables. both work similarly other than this performance issue reducing the newtwork load