Database Performance Monitor (ST04) provides a database-independent tool to analyze
and tune the following components:
< Memory and buffer usage
< Space usage
< CPU usage
< SQL requests
< Detailed SQL items
1. In the Command field, enter transaction ST04 and choose Enter (or from the SAP standard menu, choose Tools ® Administration ® Monitor ® Performance ® Database ®
ST04 - Activity).
2. An initial overview of database activity is provided which pertains to database,operating system, CPU, and memory.Microsoft SQL Server allows the analysis of specific attributes pertaining to memory, space, I/O, and quality of table reads and writes. This information can signal adjustments necessary to improve performance of the database.
a. Memory Usage Procedure cache and Data cache hit ratio can reflect memory problems.These values should be greater than95 percent for optimal memory usage.
b. Server Engine/Elapsed Shows how hard the CPU has beenworking on Microsoft SQL Serverprocesses. You are interested in theratio of busy : idle time.
c. SQL Requests Allows for snapshots of how SQL queries are utilizing table access pertaining to full table or index scans.A high ratio of full table scans vs. index scans can indicate performance bottlenecks.
d. Detail analysis menu
and tune the following components:
< Memory and buffer usage
< Space usage
< CPU usage
< SQL requests
< Detailed SQL items
1. In the Command field, enter transaction ST04 and choose Enter (or from the SAP standard menu, choose Tools ® Administration ® Monitor ® Performance ® Database ®
ST04 - Activity).
2. An initial overview of database activity is provided which pertains to database,operating system, CPU, and memory.Microsoft SQL Server allows the analysis of specific attributes pertaining to memory, space, I/O, and quality of table reads and writes. This information can signal adjustments necessary to improve performance of the database.
a. Memory Usage Procedure cache and Data cache hit ratio can reflect memory problems.These values should be greater than95 percent for optimal memory usage.
b. Server Engine/Elapsed Shows how hard the CPU has beenworking on Microsoft SQL Serverprocesses. You are interested in theratio of busy : idle time.
c. SQL Requests Allows for snapshots of how SQL queries are utilizing table access pertaining to full table or index scans.A high ratio of full table scans vs. index scans can indicate performance bottlenecks.
d. Detail analysis menu