Solution : https://service.sap.com/sap/support/notes/652634 (SAP Service marketplace login required)
Summary :
This SAP Note outlines the impactful performance variances of the SELECT ... FOR ALL ENTRIES statement in ABAP when utilized with different SAP kernels, database systems, and specific profile parameters in Microsoft SQL Server environments. The document identifies how different transformations—UNION ALL, FAE BATCH, and FAE JOIN—can affect SQL optimization based on the chosen method. It emphasizes simplicity in the SELECT statements to prevent performance degradation and suggests utilizing profile parameters or optimizer hints to enhance execution depending on the kernel version. Additionally, it advises caution when modifying parameters as they affect all ABAP reports.
Key words :
criteria union fae batch fae join================================== ======== ========== ==========average performance, dbs/mss/fae_batch = 1 dbs/mss/fae_join = 0 fae batch, dbs/mss/fae_batch = 0 dbs/mss/fae_join = 0, dbs/mss/fae_batch = 0 dbs/mss/fae_join = 1, %_hints mssqlnt 'option fae_union' note 133381 describes, profile parameters dbs/mss/fae_batch, parameters dbs/mss/fae_join, component bc-db-mss, sql server-specific database interface, rsdb/mssql/fae_join profile parameters
Related Notes :
1533640 | VLSP: performance issue while reading Handling Units |
1500503 | BI quantity conversion: Access optimization |
1286026 | Performance during SELECT from table /sapapo/ord_link (II) |
1047394 | Performance during SELECT from table /sapapo/ord_link |
1041589 | Performance when reading handling units (2) |
828147 | SQL error 8621 while processing "FOR ALL ENTRIES" statement |
766827 | Composite SAP note: Performance SCM 4.0 |
652649 | Errors in the MSSQL FOR ALL ENTRIES Batch method |
624951 | Incorrect SELECT result on SQL Server 2000 |
133381 | Database-Hints in Open SQL for MS SQL Server |
48230 | Parameters for the SELECT ... FOR ALL ENTRIES statement |
28667 | Microsoft SQL Server Specific Profile Parameters |