Which is better among FOR ALL ENTRIES and INNER JOIN iTab?

2

Performance is relatively bad with FOR ALL ENTRIES especially when the condition size is bigger. Also, one should make sure internal table is not empty as the query will then fetch all entries.
INNER JOIN iTab has better performance among the two.

2 Replies to “Which is better among FOR ALL ENTRIES and INNER JOIN iTab?”

  1. Yury says: 3 June 2021 at 10:15 pm

    are there any brawbacks of usint INNER JOIN itab ?
    maybe size restrictions of the itab or something else…?

    1. Srinidhi Raghothama says: 1 August 2021 at 8:53 pm

      There are generally no drawbacks of using INNER JOIN itab.
      For Joins, Database optimizer dynamically chooses the sequence of access based on runtime selection criteria and enables it to have fewer data blocks to be read as possible. So, Joins generally give exponentially faster performance over FAE.
      However, some results show that FAE gives better performance in following cases:
      1. If a program queries the data from same tables multiple times. FAE uses buffer and may have better performance over joins as the latter by passes the buffer.
      2. In case of Pooled/Cluster tables.

Leave a Reply

Your email address will not be published.

You may use these <abbr title="HyperText Markup Language">html</abbr> tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">

*