Sybase Responses Test
This test, executed by an internal agent, tracks the statistics pertaining to the availability and response time of the Sybase adaptive server.
Target of the test : A Sybase ASE (Below v15) server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for every Sybase server being monitored.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
Refers to the IP address of the Sybase server. |
Port |
The port number at which the Sybase server listens to. |
User |
A Sybase user who has the “sa_role”. |
Password |
The password corresponding to the above user. |
Confirm Password |
Confirm the password by retyping it here. |
Query |
By default, this parameter is set to select * from sysobjects. The test executes this executes the default query to report the availability and responsiveness of the server. If the user configured for this test does not have the right to execute the default query, then the Query parameter can be overridden with a query that user has permission to execute. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Sybase server availability |
Indicates if the database instance is responding to requests or not. |
Percent |
A value of 100 for this measure indicates that the database is responding to a request. On the other hand, a value of 0 denotes that the database is not responding. Availability problems may be caused by a misconfiguration/malfunctioning of the database instance, or because the instance is using an invalid user account. Besides the above, this measure will report that the server is unavailable even if a connection to the database instance is unavailable, or if a query to the database fails. In this case, you can check the values of the DB connection availability and Query processor availability measures to know what is exactly causing the database instance to not respond to requests - is it owing to a connection unavailability? or is it due to a query failure? |
Total response time |
Indicates the time taken by the database server to respond to a user query. This is the sum total of the connection time and query execution time. |
Secs |
A sudden increase in response time is indicative of a potential performance bottleneck on the database server. |
DB connection availability |
Indicates whether the database connection is available or not. |
Percent |
If this measure reports the value 100 , it indicates that the database connection is unavailable. The value 0 on the other hand indicates that the database connection is unavailable. A connection to the database may be unavailable if the database is down or if the database is listening on a port other than the one configured for it in the eG manager. If the Availability measure reports the value 0, then, you can check the value of this measure to determine whether/not it is due to the unavailability of a connection to the server. |
Query processor availability |
Indicates whether the database query is executed successfully or not. |
Percent |
If this measure reports the value 100, it indicates that the query executed successfully. The value 0 on the other hand indicates that the query failed. In the event that the Availability measure reports the value 0, check the value of this measure to figure out whether the failed query is the reason why that measure reported a server unavailability. |
Connection time to database server |
Indicates the time taken by the database connection. |
Secs |
A high value could indicate a connection bottleneck. Whenever the Response time of the measure soars, you may want to check the value of this measure to determine whether a connection latency is causing the poor responsiveness of the server. |
Query execution time |
Indicates the time taken for query execution. |
Secs |
A high value could indicate that one/more queries to the database are taking too long to execute. Inefficient/badly designed queries to the database often run for long periods. If the value of this measure is higher than that of the Connection time measure, you can be rest assured that long running queries are the ones causing the responsiveness of the server to suffer. |
Records fetched |
Indicates the number of records fetched from the database. |
Number |
The value 0 indicates that no records are fetched from the database |