How To Fix SMMSS_ALERTS070 - This alert shows the % of cpu time used by a single statement

SMMSS_ALERTS070 - Overview

• Message type: E = Error

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

• Message number: 070

• Message text: This alert shows the % of cpu time used by a single 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_ALERTS070 - This alert shows the % of cpu time used by a single statement ?

  The SAP error message SMMSS_ALERTS070 indicates that a specific SQL statement is consuming a high percentage of CPU time. This alert is part of the SAP Solution Manager's monitoring capabilities, which helps in identifying performance issues in the system.
  
  Cause:
  The primary cause of this alert is that a particular SQL statement is executing inefficiently, leading to high CPU usage. This can happen due to several reasons, including:
  
  Poorly Optimized Queries: The SQL statement may not be optimized, leading to excessive resource consumption.
  Lack of Indexes: Missing or improperly configured indexes can cause the database to perform full table scans instead of using indexes, which increases CPU usage.
  Data Volume: Large volumes of data being processed by the query can lead to high CPU consumption.
  Database Configuration: Suboptimal database configuration settings can also contribute to performance issues.
  Concurrency Issues: High concurrency on the same SQL statement can lead to contention and increased CPU usage.
  
  
  Solution:
  To address the issue