eG Help

A transaction is a sequence of SQL statements that are handled by the database system as a unit, in the sense that any modifications made to the database by the SQL statements are either all reflected in the state of the database, or else none of the database modifications are retained. Among other things, the transaction management functions of a database system make sure that parallel transactions from multiple database sessions are processed correctly, and that they deliver the same results as if the transactions were processed sequentially. The DbActivityTest reports statistics pertaining to the transactions executing on MaxDB.

Measurement	Description	Measurement Unit	Interpretation
Sql_command_rate	The rate at which SQL statements were executed	Commands/Sec
Sql_parsing_rate	The rate at which SQL statements were parsed	Parses/Sec
Parsed_sql_exec_rate	The rate at which parsed SQL statements were executed	Executions/Sec	A high level of parse activity when the database is running can indicate a missing statement cache implementation in your application, or a deactivated parse info cache in the JDBC interface. A high level of parse activity is normal when programs or program components are started for the first time.
Trans_commit_rate	The rate at which transactions were committed	Commits/Sec
Trans_rollback_rate	The rate at which transactions were rolled back	Rollbacks/Sec	Ideally, there should be few user rollbacks happening, since rollbacks are costly operations on the database.
Percent_rollbacks	The percentage of rollbacks	Percent	Ideally, there should be few user rollbacks happening, since rollbacks are costly operations on the database.
Memory_sort_rate	The rate at which sorting operations were performed on the main memory to build indexes	Sorts/Sec
Table_scan_rate	The rate of table scans	Scans/Sec	A high value of table scans is an indicator that the queries do not use indexes at all or use indexes with low selectivity.
Index_scan_rate	The rate of index scans	Scans/Sec