How a Health Check Saved an NHS Trust 40% in Licensing Costs

NHS Trusts operate under intense financial pressure. Every pound saved on infrastructure is a pound available for patient care. But technology estates — particularly database infrastructure — tend to grow organically over years of mergers, system implementations, and deferred maintenance. By the time anyone looks closely, the cost picture is rarely pretty.

This is the story of one Trust that looked closely, found significant waste, and acted on it.

Note: Client details have been anonymised in line with our confidentiality obligations. The financial outcomes and technical findings are accurate.

---

The Starting Point

The Trust approached SQLOPTIMISE following a merger with a neighbouring NHS organisation. The combined estate had grown to include dozens of SQL Server instances across two data centres, covering clinical systems, administrative platforms, reporting infrastructure, and legacy applications in various states of support.

Nobody had a clear picture of what was running, what it was costing, or whether the licensing in place matched actual usage.

The immediate ask: understand what we have, and identify where we can reduce spend.

---

What the Health Check Found

Over three weeks, we conducted a structured assessment of the combined SQL Server estate. The findings were significant:

Finding 1: Enterprise Edition Licences on Standard-Eligible Workloads

SQL Server Enterprise Edition carries a substantial licensing premium over Standard Edition — roughly 4x the cost per core. Enterprise is justified when you need specific Enterprise-only features: Always On Availability Groups at scale, certain compression features, advanced OLAP, or very large memory configurations.

Several of the Trust's SQL Server instances were licensed as Enterprise for workloads that used none of these features. The databases involved were small to mid-sized administrative and reporting systems with modest resource requirements and no high-availability dependencies that required Enterprise capabilities.

Remediation: Downgrade to Standard Edition on eligible instances. No application changes required. No downtime beyond the licence swap window.

Finding 2: Idle and Zombie Instances

A full inventory revealed 11 SQL Server instances that had seen no meaningful user activity in the previous 90 days. Several were running SQL Server 2012 (out of extended support since 2022). All were consuming SQL Server CAL or per-core licences.

None of these instances were monitored. None had been formally decommissioned. They simply existed — burning licensing costs and creating security exposure.

Remediation: Decommission confirmed-idle instances after a 30-day hold period. Archive data per Trust records management policy. Eliminate associated licences.

Finding 3: Consolidation Opportunities

The estate included multiple small instances running single databases with low transaction volumes. In many cases these had been spun up for specific projects or system implementations and never consolidated.

Running separate SQL Server instances for workloads that could comfortably share a single instance multiplies licensing costs unnecessarily.

Remediation: Consolidate compatible workloads onto shared instances. Apply appropriate resource governance via Resource Governor to ensure no workload can monopolise shared capacity.

Finding 4: Underutilised Azure SQL Infrastructure

Following a previous cloud migration project, the Trust had several Azure SQL databases sized at tiers that far exceeded actual workload requirements. The databases were running at Premium tier with maximum DTU allocations — for systems consuming less than 10% of provisioned capacity during peak hours.

-- Example: Checking actual DTU utilisation on Azure SQL
SELECT
    start_time,
    end_time,
    avg_cpu_percent,
    avg_data_io_percent,
    avg_log_write_percent,
    avg_memory_usage_percent
FROM sys.dm_db_resource_stats
ORDER BY end_time DESC;

Remediation: Right-size Azure SQL tiers to match actual workload. Implement auto-pause for non-production databases with infrequent access patterns.

---

The Numbers

Following the assessment, we produced a prioritised remediation plan with three tiers:

| Priority | Action | Estimated Annual Saving | |---|---|---| | P1 | Enterprise → Standard downgrades (6 instances) | £87,000 | | P1 | Decommission idle instances (11 instances) | £34,000 | | P2 | Instance consolidation (reduce 14 → 5 instances) | £42,000 | | P2 | Azure SQL right-sizing (8 databases) | £28,000 | | P3 | Additional config and security hardening | Non-financial benefit |

Total identified saving: £191,000 per year

The Trust's previous annual SQL Server licensing and infrastructure spend: approximately £460,000.

Reduction achieved within 6 months: ~40%

The health check engagement cost a fraction of the first year's savings.

---

What Made This Work

The Trust's IT leadership deserves credit for one important decision: they treated the health check as a starting point, not a box-ticking exercise.

Many organisations commission assessments and then deprioritise the findings when operational demands press in. This Trust committed to a 90-day remediation sprint on P1 items immediately after the assessment completed. The P2 items followed in the subsequent quarter.

On the technical side, the key to avoiding disruption was the sequencing: inventory and validate before any changes, decommission only after a confirmed hold period with stakeholder sign-off, and test licensing changes in a non-production environment first.

No clinical systems were affected. No unplanned downtime occurred.

---

The Broader Point

NHS licensing costs are not just a finance problem. Overspending on database infrastructure means fewer resources available elsewhere. And when SQL Server estates are unmanaged — as this one was, through no fault of the staff involved — costs compound over time.

A structured health check is the fastest way to get a clear picture and a credible plan. The work is not glamorous. But the outcomes are real.

If your SQL Server estate has grown through mergers, project-by-project expansion, or years of deferred maintenance — the chances are high that a similar picture exists. The question is whether you look for it.

---

What We Can Do For You

SQLOPTIMISE health checks are designed for exactly this kind of estate. We assess, prioritise, and provide a clear remediation roadmap — one that the internal team can execute, with our support, at whatever pace works.

The first conversation costs nothing. Get in touch →