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.
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.
are there any brawbacks of usint INNER JOIN itab ?
maybe size restrictions of the itab or something else…?
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.