HANA Connections Test

User connections to the SAP HANA database server are a good indicator of the load on the database server. If users complain about the sluggish performance of the database server, administrators may want to check the user connections to the server to figure out whether the database server is stressed due to an overload condition. If so, administrators may also want to identify the user who has imposed the maximum load on the server and the nature of that load – i.e., whether the user’s connections are active or are idle predominantly, and the maximum time for which a user connection to the server remained alive and idle. The HANA Connections test reveals all this! This test not only discovers who is currently logged into the database server, but for each login user, reports the number of open connections, the count of running and idle connections, and the duration of the oldest idle connection. This way, the test measures the current connection load on the server, points to those users who are responsible for overloading the server with numerous connections, and also indicates to administrators whether these are genuine running connections or idle connections that can be terminated to ease the strain on the server.

Target of the test : A SAP HANA Database Server

Agent deploying the test : A remote agent

Outputs of the test : One set of results for every SAP HANA database server being monitored; if the Show User flag is set to Yes, then this test will report one set of results for every user who is currently connected to the SAP HANA database server.

Configurable parameters for the test

Parameter	Description
Test period	How often should the test be executed
Host	The host for which the test is to be configured.
Port	The port number at which the specified Host listens to. By default, this will be 30015.
User	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 discussed in How to Monitor SAP HANA Database Server Using eG Enterprise?. The name of such a user has to be specified here.
Password	Enter the password of the specified User.
Confirm Password	Confirm the password by retyping it here.
IsPassive	If the value chosen for this 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.
Show User	Set this flag to Yes if you wish to view the connection details of each individual user. By doing so, each user pertaining to the SAP HANA database server will appear as a descriptor of this test. By default, this flag is set to No which implies that the TOTAL descriptor will alone appear for this test indicating the connection details of all the users collectively.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Open Connections	Indicates the number of currently open connections for this user.	Number
Idle Connections	Indicates the number of connections of this user that are currently idle on the database server.	Number	Ideally, the value of this measure should be low. A high value is indicative of a large number of idle connections, which in turn may cause unnecessary consumption of critical server resources. Idle connections also unnecessarily lock critical database objects, thereby denying other users access to those objects for performing important tasks. Use the detailed diagnosis of this measure to view the details of the idle connections.
Running Connections	Indicates the number of connections established by this user that are currently running.	Number
Oldest Connection	Indicates the maximum time duration for which a connection established by this user was idle during the last measurement time.	Secs	A low value is desired for this measure. A high value indicates that the connections to the database server have been idle for a very long time.