72
/100
B−
Health Dimensions
Executive Summary
MedBillCorp's SQL Server environment maintained 72/100 overall health in March 2026, down 6 points from February. The decline is primarily driven by two issues identified this month: a misconfigured MAXDOP setting that serialized all parallel execution plans (high impact, now resolved), and a critical security event where a legacy SA account was re-enabled outside of the change window (under investigation).
Performance fundamentals remain strong — query throughput is up 31% since DPSMF deployment in January, and 18 index recommendations have been applied, eliminating over 2 million logical reads per minute. Capacity planning flags the primary data disk as requiring expansion within 47 days — procurement action is recommended immediately.
Availability Group health is good across two of three groups. AG-CLAIMS-PROC secondary replica SQLCLM02 is showing elevated lag (8.4 seconds) and requires investigation.
Performance fundamentals remain strong — query throughput is up 31% since DPSMF deployment in January, and 18 index recommendations have been applied, eliminating over 2 million logical reads per minute. Capacity planning flags the primary data disk as requiring expansion within 47 days — procurement action is recommended immediately.
Availability Group health is good across two of three groups. AG-CLAIMS-PROC secondary replica SQLCLM02 is showing elevated lag (8.4 seconds) and requires investigation.
Recommended Actions This Month
P1
Investigate MBC_LEGACY_SA re-enablement — A privileged login was re-enabled outside of the change window with no associated ticket. Audit who performed this action and disable the account. Review all actions taken by this login since 22:47 on March 18.
P1
Expand primary data disk within 47 days — At current growth rate (+2.8GB/day), SQLPROD01 data volume will reach the 80% alert threshold around November 12. Initiate storage expansion request immediately.
P2
Investigate AG-CLAIMS-PROC replica lag — SQLCLM02 is showing 8.4 seconds of lag with 245KB send queue. This secondary has recently been reconfigured to MANUAL failover — revert to AUTOMATIC after confirming the underlying cause.
P3
Review BillingCoreExport_Hourly job impact — New hourly export job is increasing tempdb usage by ~6GB during run windows. Evaluate whether off-hours scheduling would reduce contention.
⚡
Sentinel AI generates this report automatically each month and emails it to your CTO. Configure recipients in Settings.
Configure →