Queries Grid
- The queries grid displays queries according to the timeframe control
- The queries displayed are grouped by
- The origin of the queries is the MSSQL’s This is the same reason why the queries are without actual parameters and displayed as “prepared statements.” The statistic is only recorded after the end of the execution.
- The queries grid also shows statistics of stored procedure executions. The row for stored procedure execution is colored yellow, and the text begins with “SP:”.
The queries grid exists in the following modules:
CPU Module – ordered by CPU descending
Memory module, Disk Module – ordered by Logical Reads descending
Queries Module – ordered by Duration descending
 |
|
||||||
Queries Grid Main Table
| Column | Description |
| Time | The time of the snapshot |
| Last execution | Last execution time of the query |
| Execution count | Total executions for the given query type for the timeframe |
| Duration | The sum in ms of the total durations for the given timeframe |
| CPU usage | The sum in ms of the total CPU for the given timeframe |
| Details | The first 200 characters of the text. This column is similar to the “TextData” column in the MSSQL profiler. The tooltip will present extra characters. To see the full query, press the “view details” button on the right side. |
| Physical Reads | The total physical reads for the given query. Physical reads are when there is a transfer of information from the SSD/H-disk to the memory and not when information is read from within the memory. |
| Logical Reads | The sum total of logical reads. This means a page that was found in the MSSQL cache and not brought from the SSD/H-disk. |
| Logical Writes | The sum total of logical writes. |
| Total Rows | The sum total of rows that were affected by the operation. In a select statement, the sum total of rows that were brought back to the client. |
| CLR Time | The sum total of time the query spent in CLR (associated with CPU performance). |
| Database | The original database this query was derived from. The database context depends on the active database the connection was using at that time. For example, in the management studio, the active database can be changed. The active database can also be changed in the connection string.
Note: Notice that some applications do not use the active database and use full qualifiers from ‘master’. |
| View Details | A button that opens a window with the full text of the query. |
Enhanced Charts
| Legend | |
| 1 | Chart Title |
| 2 | Save the filter/grouping button to change the display. See Filter/Grouping Options below |
| 3 | Compare button – not active in all Enhanced Charts |
| 4 | Alert indicators
Note: Alert indicators only exist if main timeframe range is under 4 hours |
| 5 | Alert lines
Only exists if the timeframe is under 4 hours (raw data analysis). |
| Physical Reads | The total physical reads for the given query. Physical reads are when there is a transfer of information from the SSD/H-disk to the memory and not when information is read from within the memory. |
| Logical Reads | The sum total of logical reads. This means a page that was found in the MSSQL cache and not brought from the SSD/H-disk. |
| Logical Writes | The sum total of logical writes. |
| Total Rows | The sum total of rows that were affected by the operation. In a select statement, the sum total of rows that were brought back to the client. |
| CLR Time | The sum total of time the query spent in CLR (associated with CPU performance). |
| Database | The original database this query was derived from. The database context depends on the active database the connection was using at that time. For example, in the management studio, the active database can be changed. The active database can also be changed in the connection string.
Note: Notice that some applications do not use the active database and use full qualifiers from ‘master’. |
| View Details | A button that opens a window with the full text of the query. |
Enhanced Charts
| Legend | |
| 1 | Chart Title |
| 2 | Save the filter/grouping button to change the display. See Filter/Grouping Options below |
| 3 | Compare button – not active in all Enhanced Charts |
| 4 | Alert indicators
Note: Alert indicators only exist if main timeframe range is under 4 hours |
| 5 | Alert lines
Only exists if the timeframe is under 4 hours (raw data analysis). |
Enhanced Chart Filter/Grouping
 |
|
||||||||||||||||
 |
Enhanced Chart Grouping Date Grouping Options. The grouping options will be enabled in correlation with the time range of the main timeframe.
None – there is no grouping. Note: If the time frame is more than 4 hours, the information brought from the repository will be brought from aggregated tables. |
||||||||||||||||
 |
Enhanced Chart Grouping Function Options By default, a grouping function is selected per
performance metric. For example, CPU will be AVG, and Duration will be SUM. However, you may select a grouping function by yourself here. Note: In some charts, like CPU, “Sum” aggregation won’t appear. |
||||||||||||||||
Compare Graphs Feature
The compare graphs feature allows the user to compare selected graphs sharing the same timeline manually. For example, if the user wishes to see the PLE chart with memory or the CPU chart with database transactions per second.
These tools will improve your ability to identify and solve performance bottlenecks.
| Legend | |
| 1 | Compare Graphs button – press to get the pop up “compare graphs” dialog. |
| 2The first/primary graph to compare | |
| 2 | Press the “Add graph” button to add additional secondary graphs to compare. |
