Documentation Index

Fetch the complete documentation index at: https://docs.fortifiedwisdom.com/llms.txt

Use this file to discover all available pages before exploring further.

Details - Query Analysis

Prev Next

The Details view shows all instances, databases, and objects a selected SQL Statement ran against during the selected time range. It cannot be opened directly; a SQL Statement must first be selected from Overview, and Details respects the same date range selected there.

Details has its own Filters panel, scoped to the selected SQL Statement:

Filter Narrows to
Instance One or more of the instances the statement ran against.
Database One or more of the databases the statement ran against.
Observations One or more of the eight Observation flags (see Overview for the full list).

Query Execution, Query CPU Usage, Query IO Usage, and Recommended Optimization are not available as filters on Details, since those narrow down which statements to look at, and Details is already scoped to one.

The selected statement is pinned at the top of the screen along with its Query Hash, and a Performance History chart plots the statement's activity over the selected range. Use the Spend, CPU, IO, Executions, or Duration toggle to change which metric the chart plots; Timeouts are shown on the chart regardless of which metric is selected. Each plot point is a total for that metric across all executions in the interval ending at that point, not an average; the interval defaults to 1 hour for the default 7-day range and can be changed with the plot-point control next to the chart. For example, a CPU plot point of 8.3 minutes means the query's executions consumed a combined 8.3 minutes of CPU time in the hour ending at that point.

Instance Breakdown

The Instance Breakdown table lists one row per instance the query ran against, with Databases and Objects columns showing the count of each. Clicking a count in either column opens a pop-up listing every database or every object involved for that instance.

Selecting a row opens the same table filtered to that instance, showing one row per database and object combination. A Back to Instance View link returns to the instance-level table.

The action icon on any row in either table provides the same View Index Analysis and Open Query ROI options available on Overview, scoped to that row's instance and database.

Selecting a row that has a specific database and object opens the Query Analysis flyout.

Clicking a Database or Instance value directly, rather than the row itself, opens the same pop-up available throughout WISdom, with options to copy the object name, or include or exclude it on the filter.

Query Analysis Flyout

The flyout displays detailed information for the selected query on the selected instance and database. It is organized into four tabs: Performance Metrics, Properties, Recommendations, Scripts, and FinOps.

Two buttons sit alongside the tabs and are available regardless of which tab is active:

  • Queue for Optimization – requests on-demand optimization for this query. This consumes one optimization credit unless the query cannot be optimized, in which case no credit is consumed. This button is shown only for a query that hasn't yet been evaluated. See Optimizations for the full credit rules.
  • Launch Savings Planner – opens the Query ROI Planner with this query's resource utilization already applied.

The area next to Launch Savings Planner reflects the query's optimization status:

Status shown Meaning
Queue for Optimization (button) The query hasn't been evaluated yet and can be queued.
Optimization in Progress The query has been queued and evaluation is running.
Optimization Ready Evaluation is complete. This covers both outcomes where WISdom finished analyzing the query: a path was found (Recommendations and Scripts are populated) or no path was found (the Recommendations tab explains why, with no Scripts to run).
Optimization Failed (shown on the Recommendations tab, no button) WISdom couldn't retrieve an execution plan for the query, so evaluation never ran. This is usually a system-level issue, such as the plan having aged out of cache or a connectivity problem reaching the instance, and can succeed on a later attempt.

Four summary metrics are shown at the top of the flyout regardless of tab: Efficiency rating, Peak Activity Hour, Annual Code Spend, and Spend per 100K Executions. Efficiency can also show as Unscored when there isn't enough data to calculate a rating for the query.

Performance Metrics

Displays a chart of Spend, CPU Usage, Executions, or IO Operations over the selected time range, along with a summary table of Average, Min, Max, and Sum for Spend, CPU Usage, I/O Operations, Executions, and Row count. As with the Performance History chart described above, each plot point on the chart is a total for the interval ending at that point, not an average.

Properties

Displays the Database(s), Object(s), Last Cache Time, Last Execution, Execution Count, and Row Count Variation for the selected query, along with its Query Hash and Plan Handle (if available).

Recommendations

Once evaluation is complete, this tab shows one of three outcomes:

  • Path found – a Query Order of Operations write-up, a plain-language walkthrough of how the query's execution plan runs, in the order SQL Server processes it, calling out the operations driving the most cost (for example, full scans, residual filters, or high-rebind spools). Below it, a numbered list of Recommendations, each labeled with a type such as Index Creation, Index Modification, or Query Rewrite, explaining the issue and the expected benefit. Matching Scripts are available on the Scripts tab.
  • Path not found – WISdom evaluated the query and determined nothing can be done to improve it. An explanation is provided, but there are no Recommendations or Scripts to act on.
  • Optimization Failed – WISdom couldn't retrieve an execution plan for the query, so it was never evaluated. This is usually a system-level issue, such as the plan having aged out of cache or a connectivity problem reaching the instance, rather than a determination about the query itself.

See Optimizations for a full walkthrough example of the Path found outcome.

Scripts

Displays the ready-to-run scripts for each recommendation shown on the Recommendations tab, such as the T-SQL to create or modify an index, or the persisted computed column changes an index may depend on.

FinOps

Displays a savings projection for the query based on a Target Optimization percentage, which defaults to 30% and can be adjusted to see how the projected ("greenline") cost changes. The chart plots current spend against optimized spend for the past 30 days, Year 1, Year 2, and Year 3, alongside Current Annual Spend, 3-Year Total Spend (Current), and 3-Year Total Spend (Optimized).

Related Topics