This section answers questions about global SAP MaxDB performance issues.
You can use Transaction ST03 or ST03N to determine how much of your system's overall response time is taken up with accessing the MaxDB database. This portion is determined by using the "Database time" column and should not exceed 40% of the overall response time.
If in addition you see Warning 3-type messages in the Database Analyzer log - especially poor data cache hit rates - then you should start a database analysis.
You can derive the database time of a transaction step from the respective statistical data record in Transaction STAD (formerly: STAT).
Note that for extremely long-running programs, there overflows may occur in the components of database time (for values > 2^32 microseconds = 71 minutes), and the subsequent time is wrongly recorded as processing time.
To determine which table accesses are mainly responsible for the database response time, you can set the stat/tabrec R/3 parameter (see Note 579462) to a value greater than 0 (-> number of tables to be logged).
If this parameter is used in connection with background jobs, the additional statistical data is not stored in the statistical record of the actual job, but in a statistical record of the RSBTCRTE report logged at the time.