On AWS, the SQL Server bill is a license bill

SQL Server 2016 reached the end of extended support on July 14, 2026. No more security updates, unless you pay for Extended Security Updates or run it somewhere that includes them. Many teams are planning upgrades and migrations right now, and many will repeat a common mistake: sizing SQL Server like any other workload.

On AWS, running SQL Server with the license included, the license is usually the largest part of the hourly price, often much larger than the compute underneath it. And SQL Server is licensed per core. That changes which levers matter.

Every vCPU you don’t need costs twice

On a general workload, an oversized instance wastes some compute. On license-included SQL Server, it also wastes license, and the license is the expensive part. That’s why the cheapest optimizations here are about cores, not instance price:

• Rightsize on real CPU use. Many SQL Server instances are sized for memory but bought as general-purpose instances, which brings cores that sit idle. Check CPU use at peak, not just on average.
• Choose memory-heavy instance families. SQL Server performance often depends more on memory (the buffer pool) than on CPU. Families with more memory per vCPU give you the same cache with fewer licensed cores.
• Use Optimize CPUs. EC2 lets you launch some instance types with fewer active cores, or with one thread per core, while keeping the instance’s full memory. Fewer cores means fewer licenses.

Standard or Enterprise

Enterprise edition costs several times more per core than Standard. Check whether you actually use Enterprise features: some features that used to require Enterprise moved to Standard years ago, and Standard’s limits are generous (in recent versions, the lesser of 4 sockets or 24 cores, and 128 GB of buffer pool memory). If a database fits those limits and doesn’t use an Enterprise-only feature, it’s paying for features it doesn’t use.

License included or bring your own

• License included (EC2 or RDS) is simple and flexible: you pay by the hour and can stop at any time.
• Bring your own license can be much cheaper if you already own licenses with Software Assurance. License Mobility lets you use them on shared AWS tenancy. Without it, you may need Dedicated Hosts, which changes the math entirely.

Run both numbers before migrating. The answer often differs between production (steady, long-lived) and development (which may qualify for the free Developer edition).

Use the end of support as leverage

An upgrade forced by end of support is a rare chance to change the whole setup at once: a newer version, the right edition, fewer cores, memory-heavy instances, and possibly RDS so patching and backups are handled for you. Treat it as a cost project as much as a version upgrade, and it can pay for itself.

The pattern holds well beyond SQL Server: whenever software is licensed per core, think about cores first and hardware second.