Count trend and comparison
The following guides you to the Counts Trend and Counts Trend Comparison menus that allow you to check and compare the database operation trends.
Counts Trend
Home > Select Project > Analysis > Counts Trend
You can check the operation trend of the key metrics of the database over time and trace the performance. You can check the current active session data and distinguish the long-running sessions.
Comparison between count trends
Home > Select Project > Analysis > Counts Trend Comparison
You can compare the count trends for different dates.
-
Select the desired instances from the Instance area. You can also select different instances.
-
Set values for Reference Date and Comparison Date.
-
Select .
Using the chart and active session area
Select on the screen. In the Layout setting window, set it to 1 x 3 and then select Save. Time must be set to Last 24 hours. You can see the database key metrics in detail for the day, as follows:
-
In Time, set a desired time interval.
- Click the green icon to select a search time.
- With the lookup period selected, select or . Then you can change the lookup time at the set time intervals.
- If you select the date and time, you can set the desired time in detail. After configuration, select Confirm.
-
Instance: You can select an instance that is connected with the project.
-
If you click a specific time point of the metrics chart, the (number3) area appears with red lines and the collected active sessions can be also displayed.
-
To change the metrics in the chart, select on the upper right.
-
The active session data is collected every 5 seconds. You can search the data by selecting the 5-second cells at the bottom of the screen.
-
To move the time by 1 minute, select or .
-
: The column header entries in the table can be displayed or hidden.
-
: You can filter the list based on the column header entries in the table. After selecting the button, you can set the conditions in each header column such as Includes, Excludes, Equal, and Unequal.
-
: You can download the content of the table as a CSV file.
Column information guide
For more information about columns, see the link.
- Active session
- Lock tree
- Process information
Item | Description |
---|---|
application | Name of the application that created the session. |
blocking_session_id | ID of the session that is blocking the current session. |
client | Name or IP address of the client that created the session. |
command | SQL command on which the session is running. (SELECT, INSERT, UPDATE, DELETE) |
completion_time | Time when the SQL operation is expected to finish. |
cpu(%) | The rate of the CPU used by the session. |
cpu_time | Amount of CPU time (milliseconds) used in the session. |
cpu_time(sigma) | Total CPU time used in all sessions. |
db | Name of the database to which the session is connected. |
elapsed_time | Elapsed time (milliseconds) since the session started. |
granted_query_memory | Amount of memory (pages) allocated for query execution. |
host | Name of the client host that created the session. |
isolation | Transaction isolation level of the current session. |
last_request_start_time | Time when the last request in the session started. |
last_wait_type | Last type that the session waited for. |
login_time | Time when the session logged into SQL Server. |
logical_reads | Number of logical reads that occurred in the session. |
logical_reads(sigma) | Total number of logical reads that occurred across all sessions. |
memory_usage | Amount of memory the session uses. |
object | Name of the database object referenced by the running SQL statement. |
objectid | ID of the object running in the session. |
percent_complete | Completion rate of the executing command. |
plan_handle | Handle that identifies the SQL plan. |
reads | Number of physical reads that occurred in the session. |
reads(sigma) | Total number of physical reads that occurred across all sessions. |
row_count | Number of rows processed in the session. |
sql_hash | Hash value of the SQL statement running in the session. |
sql_param | Parameter value of the SQL statement running in the session. |
sql_text | Entire text of the SQL statement running in the session. |
status | Current state of the session. e.g. running , suspended , etc. |
wait_resource | Resource the session is waiting on. |
wait_time | Time (milliseconds) that the session has been waiting. |
wait_type | Type of wait the session is waiting on. |
writes | Number of physical writes that occurred in the session. |
writes(sigma) | Total number of physical writes that occurred across all sessions. |
Item | Description |
---|---|
application | Name of the application that created the session. |
client | Name or IP address of the client that created the session. |
db | Name of the database to which the session is connected. |
elapsed_time | Elapsed time (milliseconds) since the session started. It is used to measure how much time has passed since a lock occurred. |
host | Name of the client host that created the session. |
id | Unique ID for the locked session. |
last_wait_type | Last type that the session waited for. |
row_count | Number of rows processed in the session. |
sql_param | Parameter value of the SQL statement running in the session. |
sql_text | Entire text of the SQL statement running in the session. |
status | Current status of the session. For example, there are running , suspended , sleeping , and such which indicate whether the session is active or waiting. |
user | Name of the user connected to SQL Server. |
wait_resource | It indicates the resource the session is waiting for. |
wait_time | Time (milliseconds) that the session has been waiting. |
wait_type | Type of wait the session is in. For example, it includes information such as lock wait or IO wait. |
The following items are the metrics collected if the XOS agent has been installed.
Item | Description |
---|---|
cputime | CPU usage time |
cpuusage | CPU Utilization |
elapse | Elapsed time of CPU usage |
vsize | Virtual memory size (Kb) |
rss | Resident Set Size (RSS) that is the number of physical pages associated with the process. |
state | Process status |
ioread | Actual time spent reading the block (milliseconds) |
iowrite | Actual time spent writing the block (milliseconds) |
pss | Process specific memory usage + Percentage of shared memory occupied by one process |
uid | user id |
cmd | Executing command |
longcmd | Full path of cmd |
WhaTap basically stores the client-related information.