topic Re: RE:Performance wise which is better in Application Development and Automation Discussions

RE:Performance wise which is better

Former Member — Fri, 26 Oct 2007 11:36:50 GMT

Hi,

Performance wise which one is better for all entries or inner joins.Can you give reasons for that.............

Regards,

Alex.

Re: RE:Performance wise which is better

Former Member — Fri, 26 Oct 2007 11:41:23 GMT

for all entries is better according to performance wise as database aaccess is less

Re: RE:Performance wise which is better

Former Member — Fri, 26 Oct 2007 11:42:11 GMT

Alex,

For all entries is better than inner joins in performance point of view

Reward points for helpful answers

Satish

Re: RE:Performance wise which is better

Former Member — Fri, 26 Oct 2007 11:42:14 GMT

it depends on number of records in tables u r joining......

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

http://www.sappoint.com/faq/faqsql.pdf

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

Re: RE:Performance wise which is better

Former Member — Fri, 26 Oct 2007 11:43:17 GMT

hi,

for all entries is the best

Re: RE:Performance wise which is better

suredarreddy_pulimamidi — Fri, 26 Oct 2007 12:28:49 GMT

SAP recommended using inner joins up to only on 3 tables. But performance wise don't use joins go for all entries. if you use joins the comparisons for your condition is takes place in database where as in for all entries it is in application server.

if helpful reward some points.

Re: RE:Performance wise which is better

Former Member — Fri, 26 Oct 2007 12:45:06 GMT

Hi!

INNER JOIN is used if we want to retrieve some data from more than one table.

FOR ALL ENTRIES is used if we want some data from a table based on some conditions of some other table.

Using several nested INNER JOIN statements can be inefficient and cause time out if the tables become too big in the future."

In ABAP, these joins are first split by the ABAP processor and then sent to the database, with the increase in DATA in production system, these joins tend to give way if your database keeps growing larger and larger.

You should rather use "FOR ALL ENTRIES IN" (Tabular conditions), which is a much efficient way as far as performance is concerned.

Check these links:

Regards

Re: RE:Performance wise which is better

Former Member — Fri, 26 Oct 2007 13:52:37 GMT

JOINS are almost always better:

<a href="/people/rob.burbank/blog/2007/03/19/joins-vs-for-all-entries--which-performs-better">JOINS vs. FOR ALL ENTRIES - Which Performs Better?</a>

Rob