Skip to end of metadata
Go to start of metadata

SAP® MaxDB - Step-by-step Guide - Procedure in a Performance Analysis


This guide deals with the analysis and optimization of performance problems.

Moderators: Christiane Hienger

WIKI Space Editor: Thiago Lüttig.


General Performance Problems in a SAP System

Performance problems in the SAP system can have a number of causes. They are not necessarily caused by the database.  If performance problems occur in the SAP system, you must first find out what causes the performance problems. You need to use transactions Workload Monitor (ST03 or ST03N) and Transaction ST06 to exclude that the problems are located in other areas, such as

The Workload Monitor (ST03 or ST03N) provides information on the distribution of the response time on CPU, database, wait time and so on. In most cases, you can use this to determine in which direction you should continue performance analysis.

Useful Information

Generally poor performance is usually analyzed by colleagues from the "Solution Optimization" area (component SV-BO). It is only once they have defined the database as the cause that the database is analyzed in detail by means of the following items in section Poor Performance in the MaxDB Database System or Poor Performance when executing Individual SQL Statements.

back to top

Poor Performance in the MaxDB Database System

If there are complaints about generally poor database performance, you should:

If you need help in analyzing the database performance you should open a customer call on component: SV-BO-DB-MAXDB

If you manage to identify costly commands with the Command Monitor, you have to optimize these under consideration of the possible Optimizer strategies, available indexes, and the table statistics (see section Poor Performance when executing Individual SQL Statements) and last but not least with the help of application development.

back to top