This test reports the count of expensive SQL statements and the maximum duration for which such statements ran.

This page depicts the default parameters that need to be configured for the HanaExpensStmtTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In order to monitor a SAP HANA database server, a special database user account with Monitoring privileges has to be created in every SAP HANA database instance that requires monitoring. The syntax of the script that is used for user creation is:

  create user <username> password <password>
  grant monitoring to <username>

  A sample script for user creation is:

  create user sapegadmin password eGurkha@123;
  grant monitoring to sapegadmin;

  The name of this user has to be specified in the USER text box.

• Specify the password of the specified USER in the PASSWORD text box.

  Note:

  The password should be alpha-numeric containing atleast one uppercase alphabet and a special character.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• In the DD RECORDS text box, specify the number of expensive SQL statements for which the detailed analysis is to be reported in the DETAILED DIAGNOSIS section. By default, the value specified in this text box is 10. Say for example, the number of expensive statements executing on the target SAP HANA database server is 15 and the value specified in the DD RECORDS is 5, then the DETAILED DIAGNOSIS section will list the detailed analysis for the top 5 expensive statements only.

• Typically, the detailed diagnosis of this test reports the top-10 (by default) queries to SAP HANA in terms of execution time. In many environments, it was noticed that the less critical background jobs (eg., Create, Alter, Backup etc.) hogged this top-10 list, because they normally take a long time to execute. The crucial user queries on the other hand, were often omitted from this top-10 list, as they usually take less time to execute than the background jobs. To enable administrators to focus on expensive user queries instead of background jobs, you can use the EXCLUDE EMPTY OBJECTS flag. By default, this flag is set to No. This means that, to identify the top-10 queries (in terms of execution time), this test will consider even those queries for which the output does not contain the object name. Since background jobs usually do not have object names in their output, this default setting implies that such jobs will by default be considered when generating detailed metrics. To disregard these jobs, set this flag to Yes. In this case, the test will only look at the execution time of those queries that return an output containing object names to generate the top-10 expensive queries list. This automatically excludes background jobs from detailed diagnosis.

• If the value chosen for the ISPASSIVE parameter is Yes, then the SAP HANA database server under consideration is a passive server in a SAP HANA cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable” by the agent if the server is not up.

• Once the necessary values have been entered, clicking on the Update button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz” and $port will be changed to “80” when configuring a test.