Skip to main content

Comparison between count trends

Info

This document has been created based on the SQL Server Monitoring V2. For the SQL Server monitoring V1 document, see the following.

Home > Select Project > Analysis > Counts Trend Comparison

You can check the operation trend of the key metrics of the database over time and trace the performance. You can also check the database operation trend by comparing the count trends on different dates. Through the Active sessions table, you can check active sessions and identify long-running sessions.

Basic screen guide

Count trend

  • If you select number 1 Base date, number 2 Comparison date, and Instance, the data is automatically applied to all widgets based on the selected items.

  • To see the meaning of the metric displayed in the widget, select Information icon next to the name or see the following.

    Note

    The tooltip of the Information Icon button is not supported in multiple languages.

  • To change the position with another widget, select and drag the upper part of the widget. However, the size of the widget cannot be changed.

  • The left of the number 3 Active sessions table displays the data for the Base date, and the right of the table displays the data for the Comparison date.

  • In the number 3 Active sessions table, the text colors are changed black → orangeRed, which means that the performance of the session is getting slower.

Selecting a comparison target

Select number 1 Base date and Instance, and then select number 2 Comparison date and Instance. You can check the data details at the time point through a tooltip that appears by hovering the mouse over the chart. The content of the tooltip is updated based on the position of the mouse.

Tooltip

  • Each series is given a unique color for easy visual distinction. The solid line represents the data in Base date, and the dotted line represents the data in Comparison date.

  • Compare Time displays the time value of the data where the mouse pointer is located.

  • It displays the metric value at the time point of the selected data, and provides the data by series. Each series includes the metric name, date, and value of the data point.

Note
  • In Database, you can select a database for comparison.

  • The colors in Database are the same in the graph chart.

Comparing the active session data

Active Sessions

  • The time zone for data retrieval can be checked in number 4.

  • Active session data is collected every 5 seconds. You can search data for the desired time by selecting the button that moves in 5-second increments on the table.

  • If you select Previous time icon or Next time icon on the upper right, you can see the data in 1-minute increments. To move in increments of 5 seconds, select 5 seconds before icon or 5 seconds after icon.

  • In the Active sessions table list, the text colors are changed black → orangeRed, which means that the performance of the session is getting slower.

  • If you click a specific time point of the graph chart, the (number 3) area appears with a red line and the collected active sessions can be also seen.

Comparing with a specific time

Number of instructions processed per second

You can compare the data by zooming in on a specific time point. Select a desired time zone to anywhere on the widgets and then drag the chart. It displays the data for a specific time zone dragged to all widgets and active session tables.

Preset

In Monitoring a Database Instance, you can load the custom widget settings and the sorted active sessions as presets.

Note

For more information about the Preset configuration, see the following.

Column information guide

For more information about columns, see the link.

ItemDescription
applicationName of the application that created the session.
blocking_session_idID of the session that is blocking the current session.
clientName or IP address of the client that created the session.
commandSQL command on which the session is running. (SELECT, INSERT, UPDATE, DELETE)
completion_timeTime when the SQL operation is expected to finish.
cpu_timeAmount of CPU time (milliseconds) used in the session.
cpu_usageIt is the CPU utilization used in the session.
dbName of the database to which the session is connected.
elapsed_timeElapsed time (milliseconds) since the session started.
granted_query_memoryAmount of memory (pages) allocated for query execution.
hostName of the client host that created the session.
idIt is the unique ID to identify the session.
instanceAgent or instance name.
isolationTransaction isolation level of the current session.
last_request_start_timeTime when the last request in the session started.
last_wait_typeLast type that the session waited for.
login_timeTime when the session logged into SQL Server.
logical_readsNumber of logical reads that occurred in the session.
memory_usageAmount of memory the session uses.
objectName of the database object referenced by the running SQL statement.
objectidID of the object running in the session.
percent_completeCompletion rate of the executing command.
plan_handleHandle that identifies the SQL plan.
queryEntire text of the SQL statement running in the session.
query_hashHash value of the SQL statement running in the session.
query_paramParameter value of the SQL statement running in the session.
readsNumber of physical reads that occurred in the session.
row_countNumber of rows processed in the session.
sql_handleIt is the unique identifier of the SQL statement.
statusCurrent state of the session. e.g. running, suspended, etc.
timeTask operation time.
userName of the user connected to SQL Server.
wait_resourceResource the session is waiting on.
wait_timeTime (milliseconds) that the session has been waiting.
wait_typeType of wait the session is waiting on.
writesNumber of physical writes that occurred in the session.
Note

WhaTap basically stores the client-related information.