> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Downgrade EC2 SQL Server Enterprise to Standard Edition

> Move EC2 instances running license-included SQL Server Enterprise to Standard Edition when they need no Enterprise features.

License-included SQL Server on EC2 adds the license to the hourly price, and Enterprise costs several times more than Standard. Many databases use no Enterprise-only features. nOps finds on-demand instances running SQL Server Enterprise that fit within Standard Edition's limits and estimates the saving at the Standard list price for the same instance.

| | |
| - | - |
| **Cloud** | AWS |
| **Category** | Database |
| **Service** | Amazon EC2 (SQL Server) |
| **Action** | Modify |
| **Effort** | High |
| **Restart needed** | Yes |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | nOps |

## Why it matters

The SQL Server license is often the largest part of the instance's cost, so the edition decides most of the bill.

## How nOps finds it

nOps reads the last 7 days of on-demand EC2 billing for instances with license-included SQL Server Enterprise on Windows or Linux. Instances with more than 48 vCPUs or more than 128 GiB of memory are left out, as they go beyond what Standard Edition can use. The saving is the on-demand cost, scaled to a month, times the difference between the Standard and Enterprise list prices for the same instance type, region and operating system. Instances not running recently, instances mostly covered by commitments or credits, and savings under \$25 a month are left out.

## Before you start

Confirm the databases use no Enterprise-only features. Permission to launch instances and migrate databases.

## How to implement

1. Check for Enterprise-only features, for example Always On availability groups beyond basic two-node groups, online index rebuilds, or features that need more cores or memory than Standard allows. The `sys.dm_db_persisted_sku_features` view lists features in use per database.
2. Launch a new instance of the same type from an AWS SQL Server Standard license-included AMI.
3. Move the databases, for example with backup and restore or log shipping, and test.
4. Cut applications over to the new instance, then terminate the old one.

## Risks and considerations

* The edition of a license-included instance is not changed in place, so this is a migration with a cutover.
* Standard Edition limits cores and buffer pool memory; check performance on the new instance.
* To roll back, keep the old instance until the new one is confirmed.

## FAQs

> [accordion] Why are large instances left out?
>
> Standard Edition can use only part of their cores and memory, so moving would leave capacity unusable.

## Related

* [Switch Non-Production RDS SQL Server to Developer Edition](https://help.nops.io/inform/supported-recommendations/switch-non-production-rds-sql-server-to-developer-edition)
* [Consolidate EC2 SQL Server Below 4 vCPUs](https://help.nops.io/inform/supported-recommendations/consolidate-ec2-sql-server-below-4-vcpus)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.