Acme Operations Portal Database Performance Review - Executive Performance Review

Section 01

Executive Summary

Decision page for business leaders: health, workload exposure, and the next approval needed.

Watch / Validate

Focused Validation

Risk signals are present; validate before committing budget.

Assessment Verdict

The environment does not show an immediate failure pattern, but it does show signals that should be validated. 0 high-signal workload items, 6 high-priority posture items, and 0 thin evidence windows should drive a focused technical review before any broad remediation spend.

The evidence window captured 15,227.5 minutes of database processing time. The largest workload item accounts for 18.6% of that time, which makes it a useful scoping lead for DBA validation, not a stand-alone reason to declare business impact.

Server Uptime

12.9 days

DMV usage window is usable

Evidence Window

15,227.5 min

Observed processing time captured by the retained evidence window.

Largest Workload Item

18.6%

Scoping cue for DBA validation, not a business incident by itself.

Dominant Wait

Other

FT_IFTSHC_MUTEX accounts for 45.8% of captured server wait time.

Decision Queue

225

Candidate actions requiring DBA owner review and validation.

Posture Review

6

High-priority health-check findings that can amplify workload pain.

Top Decisions Requested

Assign an owner for operating posture risk

6 high-priority reliability, storage, configuration, or performance hygiene items should be triaged separately from query tuning.

Medium

targets 1red/orange 0immediate 0index signals 0table signals 0posture high 6first target ops

Section 02

Business Impact Statement

Business-facing consequences and ownership cues from the collected evidence.

Workload concentration

ops: the largest observed workload item accounts for 18.6% of retained database processing time.

Use this as a validation lead. It becomes an executive issue only after the DBA team connects it to a customer workflow, batch window, service level, or labor-cost impact.

Dominant delay pattern

ops: Other is the leading wait family; FT_IFTSHC_MUTEX represents 45.8% of captured server wait time.

The leading wait family provides the first troubleshooting lane for technical validation before remediation is approved.

Operating posture exposure

6 high-priority posture items were found across reliability, storage, settings, backup, or performance hygiene.

These conditions can turn performance pain into missed service levels, operational escalations, or downtime if they are left unowned.

Section 03

Risk Register

Risks are ranked by business consequence. Likelihood reflects the next six months if no remediation or re-collection occurs.

Risk	Likelihood	Time Horizon	Business Consequence
Operating posture issue becomes an incident	High	<6 months	Reliability, storage, backup, or configuration findings can escalate from slowdowns to service disruption.

Section 04

Current State vs. Benchmark

Benchmarks are operating thresholds used for decision context, not vendor guarantees. They show relative urgency without requiring raw metric interpretation.

Workload Concentration

Customer: 18.6%Target: <20% per top workload item

Above target identifies a validation lead; it is not an executive incident without workflow impact.

Evidence History

Customer: 30.0 daysTarget: 14-30+ days

Longer retained history improves confidence in trend and regression claims.

High-Signal Workload Items

Customer: 0Target: 0 high-signal items

Each item needs validation before it becomes a change request.

Database Health Check

Customer: 6Target: 0 high-priority items

Health-check findings are business-risk contributors, not automatically root cause.

Critical Table Health

Customer: 0Target: 0 critical tables

Critical table health indicates structural risk behind recurring slowdowns.

Overall Standing

The environment is serviceable, but it has enough signals to justify a focused remediation plan and follow-up collection.

Section 05

Recommendations

Prioritized by business value: what the action fixes, what outcome it enables, and the rough level of effort.

Immediate - 0-30 DaysPrevent imminent risk

Assign an owner for operating posture risk

6 high-priority reliability, storage, configuration, or performance hygiene items should be triaged separately from query tuning.

MediumOpen detail

Strategic - 3-12 MonthsImprove resilience and planning

Create a repeatable quarterly performance review

Gives leadership a trend line for risk, evidence quality, and remediation progress.

MediumOpen detail

Section 06

Appendix - Technical Detail

The remaining sections preserve the evidence chain for technical teams. Executives can stop here unless they want supporting detail.

For Technical Teams

The supporting sections below contain database assessments, query and plan references, index analysis, table intelligence, database health checks, and collection coverage. The companion DBA report remains the authoritative place for fix validation and generated scripts.

Database AssessmentWorkload, table, index, and posture summary by targetOpen
Index Signal & AdvisementMissing, unused, duplicate, lookup-heavy, and maintenance-validation evidenceOpen
Database Health CheckBackup, reliability, storage, settings, and performance hygieneOpen
Coverage Gap AnalysisCollector inventory, row counts, failures, and evidence limitationsOpen

Disclaimer. This report presents findings from Query Store, dynamic management views, catalog views, and read-only health-check logic. All findings are observational and evidence-driven. Recommendations are directional and must be validated against application behavior, non-production testing, rollback planning, and approved change-control procedures before production deployment. Metrics represent the collection window and retained Query Store history available at execution time; live pressure can change after capture.

Section 07

ops - Database Assessment

Query Store is not leading the queue, but 6 high-priority health-check finding(s) should be reviewed.

Database Readout

ops

Query Store is not leading the queue, but 6 high-priority health-check finding(s) should be reviewed.

OPS history FULL - QS has 31 days of history. All windows fully populated.DB time hrs 253.79Max |Z| 1,634.28Top DB time 18.61%

0

Act Now

0

Red / Orange

0

Index Signals

6

High Health

Principal Narrative

Review Ranked Query is the first practical work item. The action-plan row should be validated before remediation.

The DBA should separate three questions: what query or workload is hurting, what platform condition may be contributing, and what evidence is still missing. That separation is what makes the recommendation defensible.

What To Do First

Query Store did not identify an urgent SQL regression, but 6 high-priority health-check findings should be reviewed.

ops: Review Ranked Sql Action

Action plan row returned by Query Store analysis.

Action Queue

P-

ops · Query 81333 · Plan 3017028

Review Ranked Sql Action

INVESTIGATE▸ Runbook

Action plan row returned by Query Store analysis.

OverallZ 9,792.42DB time 0%Signal RedImpact not labeled

Diagnosis

Confirm the finding is current before proposing a change.

-- Diagnosis
-- Confirm Query Store evidence, baseline quality, and recent execution pattern.
SELECT
    q.query_id,
    p.plan_id,
    rs.avg_duration,
    rs.avg_cpu_time,
    rs.avg_logical_io_reads,
    rs.count_executions
FROM sys.query_store_query AS q
JOIN sys.query_store_plan AS p
    ON p.query_id = q.query_id
JOIN sys.query_store_runtime_stats AS rs
    ON rs.plan_id = p.plan_id
WHERE q.query_id = 81333
  AND p.plan_id = 3017028;

Remediation

Translate the evidence into one controlled work item. Do not mix query, index, and setting changes in the same validation window.

Recommended next move: Review Ranked Sql Action

Why this is in the queue:
Query Store ranked this row for DBA review.

Evidence snapshot:
- query_id: 81333
- plan_id: 3017028
- DB time share: 0%
- impact score: 0
- confidence score: 0
- focus: Investigate

DBA troubleshooting path:
1. Tie this query to an application workflow, job, report, API call, or batch window.
2. Confirm Query Store history is representative: recent executions, chronic executions, baseline buckets, and plan count.
3. Inspect the current plan shape and compare it to the retained plan_id in this report.
4. Check whether waits, blocking, memory grants, tempdb, log pressure, or storage latency are amplifying this query.
5. Review linked index evidence, but treat missing-index suggestions as candidates, not final DDL.
6. Pick exactly one change lane for the validation window:
- query rewrite / parameter handling
- index candidate validation
- plan stability review
- database or instance setting review
- operating posture correction
7. Capture before metrics: duration, CPU, logical reads, writes, executions, DB time %, wait signature, and plan_id.
8. Test the smallest controlled change first. Avoid bundling unrelated query, index, and configuration changes.
9. Prepare rollback: previous DDL, dropped index recreation script, Query Store plan unforce path, or setting reversal.
10. Re-run the Sigma collection after representative workload and compare against this report.

Focus from evidence: Investigate

Validation

Re-run collection after representative workload and compare against this report.

-- Validation
-- Re-run the Sigma collection package after representative workload.
-- Compare DB time %, execution count, duration, CPU, reads, and plan_id against the baseline report.
SELECT
    q.query_id,
    p.plan_id,
    SUM(rs.count_executions) AS executions,
    AVG(rs.avg_duration) AS avg_duration,
    AVG(rs.avg_cpu_time) AS avg_cpu_time,
    AVG(rs.avg_logical_io_reads) AS avg_logical_reads
FROM sys.query_store_query AS q
JOIN sys.query_store_plan AS p
    ON p.query_id = q.query_id
JOIN sys.query_store_runtime_stats AS rs
    ON rs.plan_id = p.plan_id
WHERE q.query_id = 81333
GROUP BY q.query_id, p.plan_id
ORDER BY avg_duration DESC;

P-

ops · Query 25911539 · Plan 3969614

Review Ranked Sql Action

INVESTIGATE▸ Runbook

Action plan row returned by Query Store analysis.

OverallZ 5,131.66DB time 0%Signal RedImpact not labeled

Diagnosis

Confirm the finding is current before proposing a change.

-- Diagnosis
-- Confirm Query Store evidence, baseline quality, and recent execution pattern.
SELECT
    q.query_id,
    p.plan_id,
    rs.avg_duration,
    rs.avg_cpu_time,
    rs.avg_logical_io_reads,
    rs.count_executions
FROM sys.query_store_query AS q
JOIN sys.query_store_plan AS p
    ON p.query_id = q.query_id
JOIN sys.query_store_runtime_stats AS rs
    ON rs.plan_id = p.plan_id
WHERE q.query_id = 25911539
  AND p.plan_id = 3969614;

Remediation

Translate the evidence into one controlled work item. Do not mix query, index, and setting changes in the same validation window.

Recommended next move: Review Ranked Sql Action

Why this is in the queue:
Query Store ranked this row for DBA review.

Evidence snapshot:
- query_id: 25911539
- plan_id: 3969614
- DB time share: 0%
- impact score: 0
- confidence score: 0
- focus: Investigate

DBA troubleshooting path:
1. Tie this query to an application workflow, job, report, API call, or batch window.
2. Confirm Query Store history is representative: recent executions, chronic executions, baseline buckets, and plan count.
3. Inspect the current plan shape and compare it to the retained plan_id in this report.
4. Check whether waits, blocking, memory grants, tempdb, log pressure, or storage latency are amplifying this query.
5. Review linked index evidence, but treat missing-index suggestions as candidates, not final DDL.
6. Pick exactly one change lane for the validation window:
- query rewrite / parameter handling
- index candidate validation
- plan stability review
- database or instance setting review
- operating posture correction
7. Capture before metrics: duration, CPU, logical reads, writes, executions, DB time %, wait signature, and plan_id.
8. Test the smallest controlled change first. Avoid bundling unrelated query, index, and configuration changes.
9. Prepare rollback: previous DDL, dropped index recreation script, Query Store plan unforce path, or setting reversal.
10. Re-run the Sigma collection after representative workload and compare against this report.

Focus from evidence: Investigate

Validation

Re-run collection after representative workload and compare against this report.

-- Validation
-- Re-run the Sigma collection package after representative workload.
-- Compare DB time %, execution count, duration, CPU, reads, and plan_id against the baseline report.
SELECT
    q.query_id,
    p.plan_id,
    SUM(rs.count_executions) AS executions,
    AVG(rs.avg_duration) AS avg_duration,
    AVG(rs.avg_cpu_time) AS avg_cpu_time,
    AVG(rs.avg_logical_io_reads) AS avg_logical_reads
FROM sys.query_store_query AS q
JOIN sys.query_store_plan AS p
    ON p.query_id = q.query_id
JOIN sys.query_store_runtime_stats AS rs
    ON rs.plan_id = p.plan_id
WHERE q.query_id = 25911539
GROUP BY q.query_id, p.plan_id
ORDER BY avg_duration DESC;

P-

ops · Query 25907848 · Plan 3933046

Review Ranked Sql Action

INVESTIGATE▸ Runbook

Action plan row returned by Query Store analysis.

OverallZ 2,816.46DB time 0%Signal RedImpact not labeled

Diagnosis

Confirm the finding is current before proposing a change.

-- Diagnosis
-- Confirm Query Store evidence, baseline quality, and recent execution pattern.
SELECT
    q.query_id,
    p.plan_id,
    rs.avg_duration,
    rs.avg_cpu_time,
    rs.avg_logical_io_reads,
    rs.count_executions
FROM sys.query_store_query AS q
JOIN sys.query_store_plan AS p
    ON p.query_id = q.query_id
JOIN sys.query_store_runtime_stats AS rs
    ON rs.plan_id = p.plan_id
WHERE q.query_id = 25907848
  AND p.plan_id = 3933046;

Remediation

Translate the evidence into one controlled work item. Do not mix query, index, and setting changes in the same validation window.

Recommended next move: Review Ranked Sql Action

Why this is in the queue:
Query Store ranked this row for DBA review.

Evidence snapshot:
- query_id: 25907848
- plan_id: 3933046
- DB time share: 0%
- impact score: 0
- confidence score: 0
- focus: Investigate

DBA troubleshooting path:
1. Tie this query to an application workflow, job, report, API call, or batch window.
2. Confirm Query Store history is representative: recent executions, chronic executions, baseline buckets, and plan count.
3. Inspect the current plan shape and compare it to the retained plan_id in this report.
4. Check whether waits, blocking, memory grants, tempdb, log pressure, or storage latency are amplifying this query.
5. Review linked index evidence, but treat missing-index suggestions as candidates, not final DDL.
6. Pick exactly one change lane for the validation window:
- query rewrite / parameter handling
- index candidate validation
- plan stability review
- database or instance setting review
- operating posture correction
7. Capture before metrics: duration, CPU, logical reads, writes, executions, DB time %, wait signature, and plan_id.
8. Test the smallest controlled change first. Avoid bundling unrelated query, index, and configuration changes.
9. Prepare rollback: previous DDL, dropped index recreation script, Query Store plan unforce path, or setting reversal.
10. Re-run the Sigma collection after representative workload and compare against this report.

Focus from evidence: Investigate

Validation

Re-run collection after representative workload and compare against this report.

-- Validation
-- Re-run the Sigma collection package after representative workload.
-- Compare DB time %, execution count, duration, CPU, reads, and plan_id against the baseline report.
SELECT
    q.query_id,
    p.plan_id,
    SUM(rs.count_executions) AS executions,
    AVG(rs.avg_duration) AS avg_duration,
    AVG(rs.avg_cpu_time) AS avg_cpu_time,
    AVG(rs.avg_logical_io_reads) AS avg_logical_reads
FROM sys.query_store_query AS q
JOIN sys.query_store_plan AS p
    ON p.query_id = q.query_id
JOIN sys.query_store_runtime_stats AS rs
    ON rs.plan_id = p.plan_id
WHERE q.query_id = 25907848
GROUP BY q.query_id, p.plan_id
ORDER BY avg_duration DESC;

P-

ops · Query 25911538 · Plan 3930234

Review Ranked Sql Action

INVESTIGATE▸ Runbook

Action plan row returned by Query Store analysis.

OverallZ 1,634.28DB time 0%Signal RedImpact not labeled

Diagnosis

Confirm the finding is current before proposing a change.

-- Diagnosis
-- Confirm Query Store evidence, baseline quality, and recent execution pattern.
SELECT
    q.query_id,
    p.plan_id,
    rs.avg_duration,
    rs.avg_cpu_time,
    rs.avg_logical_io_reads,
    rs.count_executions
FROM sys.query_store_query AS q
JOIN sys.query_store_plan AS p
    ON p.query_id = q.query_id
JOIN sys.query_store_runtime_stats AS rs
    ON rs.plan_id = p.plan_id
WHERE q.query_id = 25911538
  AND p.plan_id = 3930234;

Remediation

Translate the evidence into one controlled work item. Do not mix query, index, and setting changes in the same validation window.

Recommended next move: Review Ranked Sql Action

Why this is in the queue:
Query Store ranked this row for DBA review.

Evidence snapshot:
- query_id: 25911538
- plan_id: 3930234
- DB time share: 0%
- impact score: 0
- confidence score: 0
- focus: Investigate

DBA troubleshooting path:
1. Tie this query to an application workflow, job, report, API call, or batch window.
2. Confirm Query Store history is representative: recent executions, chronic executions, baseline buckets, and plan count.
3. Inspect the current plan shape and compare it to the retained plan_id in this report.
4. Check whether waits, blocking, memory grants, tempdb, log pressure, or storage latency are amplifying this query.
5. Review linked index evidence, but treat missing-index suggestions as candidates, not final DDL.
6. Pick exactly one change lane for the validation window:
- query rewrite / parameter handling
- index candidate validation
- plan stability review
- database or instance setting review
- operating posture correction
7. Capture before metrics: duration, CPU, logical reads, writes, executions, DB time %, wait signature, and plan_id.
8. Test the smallest controlled change first. Avoid bundling unrelated query, index, and configuration changes.
9. Prepare rollback: previous DDL, dropped index recreation script, Query Store plan unforce path, or setting reversal.
10. Re-run the Sigma collection after representative workload and compare against this report.

Focus from evidence: Investigate

Validation

Re-run collection after representative workload and compare against this report.

-- Validation
-- Re-run the Sigma collection package after representative workload.
-- Compare DB time %, execution count, duration, CPU, reads, and plan_id against the baseline report.
SELECT
    q.query_id,
    p.plan_id,
    SUM(rs.count_executions) AS executions,
    AVG(rs.avg_duration) AS avg_duration,
    AVG(rs.avg_cpu_time) AS avg_cpu_time,
    AVG(rs.avg_logical_io_reads) AS avg_logical_reads
FROM sys.query_store_query AS q
JOIN sys.query_store_plan AS p
    ON p.query_id = q.query_id
JOIN sys.query_store_runtime_stats AS rs
    ON rs.plan_id = p.plan_id
WHERE q.query_id = 25911538
GROUP BY q.query_id, p.plan_id
ORDER BY avg_duration DESC;

Top Query Store Signals

ops / query 81333

RED

48,962.60

ops / query 25911539

RED

25,658.80

ops / query 25907848

RED

14,082.80

ops / query 25911538

RED

8,172.40

ops / query 25567280

RED

4,421.60

ops / query 24518899

RED

4,368.00

ops / query 23733

RED

4,047.80

ops / query 24759212

RED

3,782.10

Prioritized SQL Queue

Curated evidence for the highest-ranked Query Store rows. Full scoring detail remains in the DBA Review.

Query	DBA Focus	Signal	Overall Z	PriorityScore	ImpactLabel
81334	MONITOR	RED	203.55	1,018.2	Low Consumer
25845052	MONITOR	RED	157.32	787.1	Low Consumer
24722064	INVESTIGATE	RED	129.96	650.8	Low Consumer
25636472	MONITOR	RED	128.18	641.4	Low Consumer
25525672	INVESTIGATE	RED	111.11	556.6	Low Consumer
25991080	MONITOR	RED	109.73	549.1	Low Consumer
25991079	MONITOR	RED	104.17	521.4	Low Consumer
25524497	INVESTIGATE	RED	85.74	430.2	Low Consumer
25834933	MONITOR	RED	81.37	407.3	Low Consumer
19740401	INVESTIGATE	RED	80.15	402.3	Low Consumer
81333	MONITOR	RED	9792.42	48,962.6	Low Consumer
25911539	MONITOR	RED	5131.66	25,658.8	Low Consumer
25907848	MONITOR	RED	2816.46	14,082.8	Low Consumer
25911538	INVESTIGATE	RED	1634.28	8,172.4	Low Consumer
25567280	MONITOR	RED	884.22	4,421.6	Low Consumer
24518899	MONITOR	RED	873.50	4,368	Low Consumer
23733	INVESTIGATE	RED	809.26	4,047.8	Low Consumer
24759212	MONITOR	RED	756.33	3,782.1	Low Consumer
25837015	MONITOR	RED	427.73	2,139.2	Low Consumer
19765303	INVESTIGATE	RED	227.46	1,138.8	Low Consumer
25682352	MONITOR	RED	226.00	1,130.5	Low Consumer
25265532	INVESTIGATE	RED	20.16	101.8	Low Consumer
23470735	INVESTIGATE	RED	17.56	89.3	Low Consumer
2814593	INVESTIGATE	RED	16.45	83.8	Low Consumer
25885802	MONITOR	RED	16.54	83.2	Low Consumer
25918003	INVESTIGATE	RED	16.02	81.1	Low Consumer
13124260	INVESTIGATE	RED	15.59	79.5	Low Consumer
25989913	MONITOR	RED	15.53	78.1	Low Consumer
25886466	INVESTIGATE	RED	14.46	73.3	Low Consumer
25935447	MONITOR	RED	75.66	378.8	Low Consumer

Showing 30 of 50 rows. Full data is available in CSV output.

Index Intelligence

0

OPS missing indexes

0

Dead indexes

0

Duplicate groups

0

Maintenance validation

No Query Store-validated missing-index rows were returned.

Database Health Check

6

Priority <= 100

23

Priority 101-200

39

Health findings

652

Hot table rows

Priority	FindingsGroup	Finding	DatabaseName
200	Backup	MSDB Backup History Not Purged	msdb
210	Backup	Differential Backups Stale or Missing	ops
210	Backup	Differential Backups Stale or Missing	MDW
150	TempDB	Uneven TempDB File Sizes	tempdb
200	Security	DATABASE OWNER NOT SA	ops
230	Security	Jobs Owned By Users	—
230	Security	Jobs Owned By Users	—
230	Security	Jobs Owned By Users	—

Showing 8 of 39 rows. Full data is available in CSV output.

Section 08

Index Signal & Advisement

Oracle index advisement is represented here by a blended view of Query Store-validated missing-index candidates, unused-index debt, duplicate/overlap groups, lookup exposure, and fragmentation candidates.

0

OPS missing indexes

0

Dead indexes

0

Duplicate groups

0

Lookup exposure

0

Rebuild candidates

Database	MissingIndexCandidates	DeadIndexes	DuplicateGroups	LookupQueries	RebuildCandidates	TotalIndexSignals
ops	0	0	0	0	0	0

Top Query Store-Validated Missing Index Candidates

Candidates are only shown when tied back to ranked Query Store plans.

No Query Store-validated missing-index candidates were returned.

Section 09

Database Health Check

This is the module counterpart to Oracle database health checks. The executive review only surfaces health-check findings when settings, storage, tempdb/log configuration, reliability, or performance hygiene can influence the priority story.

Priority <= 100

6

Highest-priority health-check findings

Priority 101-200

23

Scheduled DBA review findings

Total Findings

39

Rows emitted by health-check collection

Finding Groups

7

Distinct evidence families

Health Check Finding Groups

Grouped view of the highest-volume and highest-priority health-check findings.

FindingsGroup	Count	TopPriority	TopFinding
Security	14	120	xp_cmdshell Enabled
Reliability	10	120	Agent Jobs Failing Recently
Performance	8	100	Many Plans for One Query
Backup	3	200	MSDB Backup History Not Purged
File Configuration	2	150	Data and Log on Same Drive
TempDB	1	150	Uneven TempDB File Sizes
Features	1	230	Service Broker Disabled

Top Health Check Findings

Highest-priority health-check findings for DBA review.

Database	Priority	FindingsGroup	Finding	DatabaseName
ops	100	Performance	Many Plans for One Query	—
ops	100	Performance	Many Plans for One Query	—
ops	100	Performance	Many Plans for One Query	—
ops	100	Performance	Many Plans for One Query	—
ops	100	Performance	Many Plans for One Query	—
ops	100	Performance	Many Plans for One Query	—
ops	120	Reliability	Agent Jobs Failing Recently	—
ops	120	Reliability	Agent Jobs Failing Recently	—
ops	120	Security	xp_cmdshell Enabled	—
ops	150	File Configuration	Data and Log on Same Drive	ops
ops	150	File Configuration	Data and Log on Same Drive	MDW
ops	150	Performance	Plan Cache Adhoc Bloat (heuristic)	—
ops	150	Security	Public CONNECT on Endpoints	—
ops	150	Security	Public CONNECT on Endpoints	—
ops	150	Security	Public CONNECT on Endpoints	—
ops	150	Security	Public CONNECT on Endpoints	—

Section 10

Coverage Gap Analysis & Execution Log

Collection inventory and execution trace are preserved here for audit, re-collection, and evidence-chain review.

Diagnostic Topic Coverage MatrixView evidence

What this report covers, what is partial, and what should be re-collected before making a stronger claim.

Topic	Status	Notes
Collector Mode	Complete	Fast Regression Triage selected which collector families were run.
Summary & High-Level Observation	Covered	Section 01 plus per-target narrative and decision ledger.
Top Query Statements by Priority	Covered	Query Store regression RS1 ranked by status, score, and DB-time share.
Z-Score Regression Breakdown	Covered	Per-query z-score detail by CPU, reads, duration, and baseline quality.
Chronic Cost / DB-Time Share	Covered	Queries consuming the largest share of retained workload cost.
Wait Statistics	Covered	Server-level wait profile from sys.dm_os_wait_stats and per-query wait category breakdown from Query Store when available.
File I/O, Memory, and TempDB	Covered	Dedicated resource collector for file latency, memory configuration, memory grants, TempDB posture, and synthesized resource findings.
Plan Intelligence	Covered	Query Store plan count, plan-shape flags, forced-plan state, baseline/current comparison, and support-ready plan SQL.
Table Intelligence	Skipped	Object-level workload heat, access-path pressure, and query participation.
Table Health	Skipped	Stale statistics, heaps, disabled objects, partition skew, lock waits, and storage signals.
Recommended Actions & Runbooks	Covered	Per-target action plan cards with validation SQL.
Index Intelligence	Covered	Unused, duplicate, lookup-heavy, missing-index, and maintenance-validation evidence.
Database Health Check	Partial	Settings, storage, backup/reliability, tempdb/log, security, and performance hygiene.
Execution Coverage	Complete	22/22 result sets succeeded.

Collection Package InventoryView evidence

Chain-of-custody view for offline delivery. A customer DBA can run the standardized read-only package, return these outputs, and import them without direct server credentials.

Collector Script	Evidence Family	Result Sets	Rows	Status	Report Use
Sigma Collection Profile	Imported evidence	1	13	Captured	Coverage and supporting evidence
Sigma_Script10_ResourceDiagnostics.sql	Query Store regression, z-score baselines, action plan, table heat	6	46	Captured	Executive summary, DBA scoring matrix, runbook actions
Sigma_Script1_v2.sql	Query Store regression, z-score baselines, action plan, table heat	8	1,078	Captured	Executive summary, DBA scoring matrix, runbook actions
Sigma_Script4_LookupExplosion.sql	Lookup-heavy query and index coverage review	3	1	Captured	Index signal and advisement sections
Sigma_Script6_DatabaseHealthCheck.sql	Database health check	1	39	Captured	Database health check impacts and DBA health-check tab
Sigma_Script9_WaitStats.sql	Wait statistics	3	231	Captured	Wait Analysis tab, dashboard wait signature, executive dominant wait KPI

Execution TraceView evidence

Collector-level success, row count, duration, and error evidence for audit and re-collection decisions.

Database	ResultSetName	ScriptName	Rows	Success	DurationMs	ErrorMessage
ops	SqlServer_QueryStoreRegression_RS0	Sigma_Script1_v2.sql	1	True	38	—
ops	SqlServer_QueryStoreRegression_RS1	Sigma_Script1_v2.sql	50	True	2	—
ops	SqlServer_QueryStoreRegression_RS2	Sigma_Script1_v2.sql	50	True	1	—
ops	SqlServer_QueryStoreRegression_RS3	Sigma_Script1_v2.sql	50	True	2	—
ops	SqlServer_QueryStoreRegression_RS4	Sigma_Script1_v2.sql	0	True	1	—
ops	SqlServer_QueryStoreRegression_RS5	Sigma_Script1_v2.sql	225	True	3	—
ops	SqlServer_QueryStoreRegression_RS6	Sigma_Script1_v2.sql	652	True	8	—
ops	SqlServer_QueryStoreRegression_RS7	Sigma_Script1_v2.sql	50	True	1	—
ops	SqlServer_LookupExplosion_RS0	Sigma_Script4_LookupExplosion.sql	1	True	1	—
ops	SqlServer_LookupExplosion_RS1	Sigma_Script4_LookupExplosion.sql	0	True	1	—
ops	SqlServer_LookupExplosion_RS2	Sigma_Script4_LookupExplosion.sql	0	True	1	—
ops	SqlServer_PlatformPosture_RS0	Sigma_Script6_DatabaseHealthCheck.sql	39	True	1	—
ops	SqlServer_WaitStats_RS0	Sigma_Script9_WaitStats.sql	30	True	1	—
ops	SqlServer_WaitStats_RS1	Sigma_Script9_WaitStats.sql	200	True	1	—
ops	SqlServer_WaitStats_RS2	Sigma_Script9_WaitStats.sql	1	True	1	—
ops	SqlServer_ResourceDiagnostics_RS0	Sigma_Script10_ResourceDiagnostics.sql	1	True	2	—
ops	SqlServer_ResourceDiagnostics_RS1	Sigma_Script10_ResourceDiagnostics.sql	13	True	1	—
ops	SqlServer_ResourceDiagnostics_RS2	Sigma_Script10_ResourceDiagnostics.sql	9	True	1	—
ops	SqlServer_ResourceDiagnostics_RS3	Sigma_Script10_ResourceDiagnostics.sql	9	True	1	—
ops	SqlServer_ResourceDiagnostics_RS4	Sigma_Script10_ResourceDiagnostics.sql	1	True	1	—
ops	SqlServer_ResourceDiagnostics_RS5	Sigma_Script10_ResourceDiagnostics.sql	13	True	1	—
ops	SqlServer_CollectionManifest_RS0	Sigma Collection Profile	13	True	1	—

Acme Manufacturing Operations Portal Production Database Performance Review

Executive Summary

Business Impact Statement

Risk Register

Current State vs. Benchmark

Recommendations

Appendix - Technical Detail

For Technical Teams

ops - Database Assessment

ops

Index Signal & Advisement

Database Health Check

Coverage Gap Analysis & Execution Log