# SQL Server Enterprise Edition on EC2 Without Enterprise Feature Use

Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/sql-server-enterprise-edition-on-ec2-without-enterprise-feature-use

SQL Server on EC2 is frequently deployed as Enterprise edition by default: it is picked from an AMI list, inherited from an on-premises build, or...

By: PointFive

Updated: 2026-09-28

[Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) 

The short version

SQL Server on EC2 is frequently deployed as Enterprise edition by default: it is picked from an AMI list, inherited from an on-premises build, or chosen to avoid future limits.

PointFive Research

Cloud cost research at PointFive

AWS service

[AWS EC2](https://www.pointfive.co/efficiency-hub/cloud-services/aws-ec2)

Category

[Databases](https://www.pointfive.co/efficiency-hub/service-category/databases)

Reference

CER-0346

Type

Suboptimal Tier or SKU

## Explanation

Why the waste happens and who it affects.

Many of these databases never use an Enterprise-only feature. Enterprise is significantly more expensive than Standard whether the license is included in the EC2 hourly rate or brought by the customer; in an AWS Prescriptive Guidance comparison of license-included r6i.xlarge instances in us-east-1, the Standard SQL Server license cost 68 percent less than Enterprise. Every such instance pays that premium for capability it does not use.

The gap persists because feature use is invisible from the infrastructure side: the instance looks healthy and correctly sized. AWS Compute Optimizer addresses this directly with commercial software license recommendations for SQL Server on EC2, which flag Enterprise licenses whose features are not in use and recommend downgrading to Standard, or to Developer edition for non-production workloads.

## Billing model

The pricing dimensions that drive this cost.

License-included instance

The EC2 hourly rate for Windows with SQL Server includes the SQL Server license, which is bound to the AMI's billing code; Enterprise is billed at a higher rate than Standard on the same instance type

Bring your own license

The customer supplies SQL Server licenses, so an Enterprise instance consumes the more expensive Enterprise licenses

Developer edition

Free of SQL Server license cost but only eligible for non-production, development and test workloads

## How to detect

6 checks to find it in your estate.

- Enable AWS Compute Optimizer license recommendations for SQL Server: it discovers SQL Server instances by inferred workload type and, once CloudWatch Application Insights is set up with read-only database credentials, analyzes the mssql\_enterprise\_features\_used metric

- Review Compute Optimizer license findings: Not optimized with the reason LicenseOverprovisioned means none of the paid Enterprise features were used; Insufficient metrics means Application Insights is not configured and the instance has not been evaluated

- Inventory SQL Server instances by edition and licensing model (license-included AMIs versus BYOL), and prioritize Enterprise instances in non-production environments

- Use the AMI billing codes (billing product) on each instance to confirm which SQL Server edition is actually being billed, since changing the edition inside the operating system does not change license-included billing

- Run SELECT feature\_name FROM sys.dm\_db\_persisted\_sku\_features in each database to list persisted Enterprise features, and manually check features that do not show there, such as online index rebuilds in maintenance jobs

- Check the in-place downgrade constraints AWS lists for each candidate: fewer than 48 vCPUs and 128 GiB of memory, and no use of database-level Enterprise features, Always On availability groups, online index operations, Resource Governor, peer-to-peer or Oracle replication, R or Python extensions, or memory-optimized tempdb metadata

## How to fix

5 ways to remove the waste.

- For BYOL Enterprise instances that meet the requirements, perform an in-place edition downgrade to Standard (or Developer for non-production); AWS publishes a Systems Manager document and evaluation script for this

- For license-included Enterprise instances, which are not eligible for an in-place downgrade and whose billing is bound to the AMI, migrate the databases to a new instance launched from a SQL Server Standard license-included AMI and retire the Enterprise instance

- If an instance exceeds the Standard edition resource limits only because it is oversized, rightsize it first so that it qualifies for Standard

- Validate less common Enterprise features against the Microsoft edition comparison for the SQL Server version in use before downgrading, and test on a copy of the database

- Set Standard (or Developer for non-production) as the default edition in AMI catalogs and provisioning templates so new instances do not start on Enterprise

## Documentation

Vendor references for pricing and configuration.

- [Viewing commercial software license recommendations  docs.aws.amazon.com](https://docs.aws.amazon.com/compute-optimizer/latest/ug/view-license-recommendations.html)

- [Optimize SQL Server licensing by using Compute Optimizer  docs.aws.amazon.com](https://docs.aws.amazon.com/prescriptive-guidance/latest/optimize-costs-microsoft-workloads/sql-server-compute-optimizer.html)

- [Evaluate if you can downgrade your Microsoft SQL Server edition  docs.aws.amazon.com](https://docs.aws.amazon.com/sql-server-ec2/latest/userguide/downgrade-sql-server-on-ec2.html)

- [Compare SQL Server editions  docs.aws.amazon.com](https://docs.aws.amazon.com/prescriptive-guidance/latest/optimize-costs-microsoft-workloads/sql-server-editions.html)

- [Amazon EC2 On-Demand Pricing  aws.amazon.com](https://aws.amazon.com/ec2/pricing/on-demand/)

## Related inefficiencies

[Browse the library](https://www.pointfive.co/efficiency-hub)

- AWS EC2  CER-0347

### [SQL Server on EC2 Instances Below the 4-vCPU License Minimum](https://www.pointfive.co/efficiency-hub/inefficiencies/sql-server-on-ec2-instances-below-the-4-vcpu-license-minimum)

Under Microsoft's SQL Server core licensing rules, each server running SQL Server must be licensed for a minimum of four cores, so an EC2 instance with one or two vCPUs running SQL Server under bring-your-own-license still needs four core...

Databases

- AWS EC2  CER-0348

### [SQL Server Instances Exceeding Edition vCPU Limits on EC2](https://www.pointfive.co/efficiency-hub/inefficiencies/sql-server-instances-exceeding-edition-vcpu-limits-on-ec2)

SQL Server Standard and Web editions cap how much compute a single SQL Server instance can use. Standard is limited to the lesser of 4 sockets or 24 cores, which AWS expresses as 48 vCPUs on EC2, and Web is limited to the lesser of 4...

Databases

- AWS EC2  CER-0158

### [Inefficient Processor Selection in EC2 Instances](https://www.pointfive.co/efficiency-hub/inefficiencies/inefficient-processor-selection-in-ec2-instances)

Many organizations default to Intel-based EC2 instances due to familiarity or assumptions about workload compatibility. However, AWS offers AMD and Graviton-based alternatives that often deliver significantly better price-performance for...

Compute

---
Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.

