Db Activity Test
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 Db Activity test reports statistics pertaining to the transactions executing on MaxDB.
Target of the test : A MaxDB server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for the MaxDB server being monitored.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The host name of the server for which the test is to be configured. |
Port |
The port number to which the server is listening. |
DatabaseName |
The test connects to a database on MaxDB and extracts performance statistics from the system tables in the database. Therefore, provide the name of a database in the DatabaseName text box. |
Username |
Since users with the SYSDBA privilege alone are allowed access to system tables, specify the name of such a user against Username. |
Password |
Provide the Password that corresponds to the specified Username. |
Confirm Password |
Confirm the password by retyping it here. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Sql command rate |
Indicates the rate at which SQL statements were executed. |
Commands/Sec |
|
Sql parsing rate |
Indicates the rate at which SQL statements were parsed. |
Parses/Sec |
|
Parsed sql execution rate |
Indicates 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. |
Transaction commits |
Indicates the rate at which transactions were committed. |
Commits/Sec |
|
Transaction rollbacks |
Indicates 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. |
Rollbacks |
Indicates the percentage of rollbacks. |
Percent |
Ideally, there should be few user rollbacks happening, since rollbacks are costly operations on the database. |
Memory sort rate |
Indicates the rate at which sorting operations were performed on the main memory to build indexes. |
Sorts/Sec |
|
Table scans |
Indicates 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 |
Indicates the rate of index scans. |
Scans/Sec |
|