Findings

WISdom evaluates these rules against every minute of a selected range. When a rule matches, it becomes a finding on the What Happened? screen with its own supporting information and three ranked resolutions.

Each page here carries the full definition. The short version, the one or two lines you see in the app behind What this rule checks, is the opening of the same article, so the product and the documentation always say the same thing.

Resolutions are ranked, and the ranking is deliberate. Option 1 fixes the cause where it lives and costs nothing. Option 2 changes the application or mitigates the impact. Option 3 adds resource or escalates, which is the option that spends money, so it is always last.

Finding	Category	What it detects
Resource-Heavy Query	Query & Session	One session ran a single statement that consumed far more CPU, logical reads, or writes than anything else active in that minute.
Duplicate Query Storm	Query & Session	The identical statement, matched by query hash, was executing in many sessions at the same moment.
Application Overload	Query & Session	One application, identified by its program name, held an unusually large number of concurrent sessions against the instance.
Blocking	Blocking & Deadlocks	One session held locks that other sessions were waiting behind, forming a chain.
Deadlock	Blocking & Deadlocks	Two or more transactions blocked each other in a cycle that could not resolve, so SQL Server chose a victim and rolled its transaction back.
High Query Concurrency	CPU	An unusually large number of sessions were running or runnable at the same moment.
Buffer Pool Pressure	Memory	Page Life Expectancy, the average time a data page survives in the buffer pool before being evicted, dropped well below its normal level.
Excessive Plan Compilation	CPU	SQL Server compiled new plans at a much higher rate than normal.
Excessive Plan Recompilation	CPU	Cached plans that were still valid were discarded and rebuilt at a much higher rate than normal.
Transaction Surge	Throughput	Committed transactions per second across the databases rose well above the normal rate for this time of day.
Resource Bottleneck	Waits	One wait category accounted for most of the waiting across active sessions this minute.
Database CPU Pressure	CPU	WISdom’s composite CPU pressure score for this database, on a 0 to 100 scale, was high for the minute.
Database Contention Pressure	Contention	WISdom’s composite contention pressure score for this database, on a 0 to 100 scale, was high for the minute.
Database Memory Pressure	Memory	WISdom’s composite memory pressure score for this database, on a 0 to 100 scale, was high for the minute.
Database Storage Pressure	Storage	WISdom’s composite storage pressure score for this database, on a 0 to 100 scale, was high for the minute.
Host CPU Pressure	CPU	WISdom’s composite CPU pressure score for the host, on a 0 to 100 scale, was high for the minute.
Host Memory Pressure	Memory	WISdom’s composite memory pressure score for the host, on a 0 to 100 scale, was high for the minute.
Host Storage Pressure	Storage	WISdom’s composite storage pressure score for the host, on a 0 to 100 scale, was high for the minute.
Connection Surge	Throughput	The number of user connections to the instance rose well above its normal level for this time of day.