How To Fix SMMSS_ALERTS072 - &1% of logical reads caused by one statement

SAP Error Message - Details

• Message type: E = Error

• Message class: SMMSS_ALERTS - Message class for MSSQL rz20 messages

• Message number: 072

• Message text: &1% of logical reads caused by one statement

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message SMMSS_ALERTS072 - &1% of logical reads caused by one statement ?

  The SAP error message SMMSS_ALERTS072 indicates that a specific SQL statement is causing a high number of logical reads, which can lead to performance issues in the system. The message typically includes a percentage value indicating the proportion of logical reads attributed to that particular statement.
  Cause:
  
  
  Inefficient SQL Query: The SQL statement may not be optimized, leading to excessive logical reads. This can happen due to:
  
  Missing indexes on the tables being queried.
  Poorly written joins or subqueries.
  Retrieving more data than necessary (e.g., using SELECT * instead of specifying required columns).
  
  
  
  Data Volume: The volume of data being processed can also contribute to high logical reads, especially if the tables involved are large and not properly indexed.
  
  
  Database Configuration: Sometimes, the database configuration settings may not be optimal for the workload, leading to inefficient execution plans.
  
  
  Solution:
  
  
  Analyze the SQL Statement:
  
  Use tools like SQL Trace (ST05) or SQL Performance Analysis to identify the problematic SQL statement.
  Review the execution plan to understand how the database is processing the query.
  
  
  
  Optimize the Query:
  
  Rewrite the SQL statement to make it more efficient. This may involve:
  
  Adding appropriate indexes to the tables involved.
  Reducing the number of columns retrieved.
  Simplifying joins or breaking down complex queries into smaller parts.
  
  
  
  
  
  Database Tuning:
  
  Review and adjust database parameters that may affect performance.
  Ensure that statistics are up to date, as outdated statistics can lead to suboptimal execution plans.
  
  
  
  Monitor and Test:
  
  After making changes, monitor the performance to ensure that the number of logical reads has decreased.
  Test the changes in a development or quality assurance environment before applying them to production.
  
  
  
  Related Information:
  
  Transaction Codes: Use transaction codes like ST04 (Database Performance Monitor) and ST05 (SQL Trace) to analyze performance issues.
  SAP Notes: Check SAP Notes for any known issues or recommendations related to the specific SQL statement or transaction causing the error.
  Performance Tuning Guides: Refer to SAP's performance tuning guides for best practices on optimizing SQL queries and database performance.
  
  By addressing the underlying causes of the high logical reads, you can improve the performance of the affected SQL statement and reduce the impact on the overall system.