Methodology

CPU identifies the opportunity. Every required resource must support the target.

The assessment evaluates exact AWS-orderable candidates against collected workload evidence. It does not approve a smaller configuration from average CPU alone.

CPU

How it is assessed

Your measured busy periods, not averages, are tested against each smaller size.

Candidate passes whenThe smaller size handles your busy periods with a safety margin.
Memory

How it is assessed

Page life expectancy (how long data stays in memory) shows whether memory is under stress.

Candidate passes whenMemory goes down only as far as page life expectancy allows: up to two steps with no stress, one step with light stress, none under stress.
IOPS

How it is assessed

Disk operations are measured over the whole collection window.

Candidate passes whenThe smaller size supports your disk activity, including busy periods.
Throughput

How it is assessed

Data transfer is measured separately from disk operations.

Candidate passes whenThe smaller size supports your data transfer, including busy periods.
tempdb and storage

How it is assessed

tempdb use and your current storage setup are checked.

Candidate passes whenYour storage and tempdb keep working on the smaller size.
Available in AWS

How it is assessed

The exact size is checked for your Region, edition, SQL Server version, and Multi-AZ setup.

Candidate passes whenAWS offers the exact target, and a separate verification check agrees.

Possible outcomes

One clear answer per workload.

  1. Optimized: a smaller size passed every check.
  2. As is: no smaller size passed every check, so the workload stays on its current setup.
  3. More evidence needed: the report names what is missing instead of guessing.

See how the result is presented

See how a report is laid out, from the result to the technical evidence.

View Sample Report