How To Fix SMMSS_ALERTS091 - This alert shows the object causing high logical reads

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 091

• Message text: This alert shows the object causing high logical reads

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_ALERTS091 - This alert shows the object causing high logical reads ?

  The SAP error message SMMSS_ALERTS091 indicates that there is an object (such as a table or index) in the SAP system that is causing high logical reads. High logical reads can lead to performance issues, as they indicate that the database is being accessed frequently, which can consume resources and slow down the system.
  Cause
  The primary causes of high logical reads can include:
  
  Inefficient Queries: Poorly written SQL queries that do not use indexes effectively can lead to high logical reads.
  Lack of Indexes: Missing or improperly configured indexes on tables can cause the database to perform full table scans instead of using indexes to retrieve data.
  Data Volume: Large volumes of data in tables can lead to increased logical reads, especially if the queries are not optimized.
  Frequent Access Patterns: Certain transactions or reports may access the same data repeatedly, leading to high logical reads.
  Database Configuration: Suboptimal database configuration settings can also contribute to performance issues.
  
  Solution
  To address the high logical reads indicated by the SMMSS_ALERTS091 alert, consider the following steps:
  
  
  Analyze the Query: Use transaction codes like ST05 (SQL Trace) or ST12 (Single Transaction Analysis) to trace the SQL statements that are causing high logical reads. Look for inefficient queries that can be optimized.
  
  
  Optimize SQL Statements: Rewrite or optimize the SQL queries to reduce the number of logical reads. This may involve:
  
  Adding or modifying indexes.
  Using more selective WHERE clauses.
  Avoiding SELECT * and only selecting necessary columns.
  
  
  
  Index Management: Review the indexes on the affected tables. Consider:
  
  Creating new indexes if they are missing.
  Dropping unused or redundant indexes that may be causing overhead.
  Rebuilding fragmented indexes.
  
  
  
  Database Statistics: Ensure that database statistics are up to date. Outdated statistics can lead to suboptimal query plans. Use the appropriate commands to gather statistics for the affected tables.
  
  
  Monitor and Tune: Continuously monitor the performance of the system using tools like SAP Solution Manager or database monitoring tools. Regularly review and tune queries and indexes as data volumes and access patterns change.
  
  
  Consult Documentation: Refer to SAP notes and documentation for specific guidance related to the version of SAP you are using, as there may be known issues or recommendations.
  
  
  Related Information
  
  Transaction Codes: ST05 (SQL Trace), ST12 (Single Transaction Analysis), SE11 (Data Dictionary), SE14 (Database Utility).
  Performance Tuning: Familiarize yourself with SAP performance tuning best practices and guidelines.
  SAP Notes: Check SAP Notes for any specific recommendations or patches related to performance issues.
  Database Administration: Work closely with your database administrator (DBA) to ensure that the database is configured optimally and that best practices are being followed.
  
  By following these steps, you can identify the root cause of the high logical reads and implement solutions to improve the performance of your SAP system.