SAP Knowledge Base Article - Preview

2637345 - Expensive SQL with missing where predicates from FAE statements


To be applicable, all three of the following symptoms must be observed:

  • You notice long-running/expensive SQL queries running in SM50/SM66 (sequential read) or find exepensive SQL in an ST12/ST05 trace.

ST05 - expensive statement.PNG


  • The expensive statement contains no predicates in the WHERE clause except for the client (MANDT/MANDANT/CLIENT).

ST05 - native statement.PNG


  • The ABAP statement (from which the native SQL originates) contains a FOR ALL ENTRIES (FAE) clause.

If the query is captured in an ST05 trace, select the problem line and click the Display ABAP Call Location button

ST05 - ABAP code location.PNG

And ST05 will take you to the source of the SQL statement

ST05 - Call Location.PNG



SAP Netweaver


ABAP platform all versions ; SAP NetWeaver all versions


IS NOT INITIAL , KBA , performance , SV-PERF , Performance Problems , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.