# SQL Server Instances Exceeding Edition vCPU Limits on EC2 Canonical: 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. By: PointFive Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) The short version SQL Server Standard and Web editions cap how much compute a single SQL Server instance can use. 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-0348 Type Overprovisioned Resource ## Explanation Why the waste happens and who it affects. 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 sockets or 16 cores, or 32 vCPUs. When SQL Server Standard or Web runs on an EC2 instance with more vCPUs than that, the extra vCPUs cannot be used by the database engine, but the instance and its licensing are still billed in full. This usually happens when an instance is sized for memory or storage throughput and the chosen size happens to come with more vCPUs, when a workload is lifted from a larger on-premises server, or when an instance is scaled up during an incident and never scaled back. AWS Trusted Advisor flags these instances in its check Amazon EC2 instances over-provisioned for Microsoft SQL Server, noting that an over-provisioned instance pays full price without any performance improvement. ## Billing model The pricing dimensions that drive this cost. Instance-hour rate EC2 instance charges rise with instance size, so vCPUs above the edition cap are paid for but idle for SQL Server License-included SQL Server The SQL Server license is part of the hourly rate of the SQL Server AMI and scales with the instance size, including vCPUs the edition cannot use Edition compute cap Standard edition can use up to 48 vCPUs and Web edition up to 32 vCPUs per SQL Server instance on EC2 ## How to detect 4 checks to find it in your estate. - Review the Trusted Advisor cost optimization check Amazon EC2 instances over-provisioned for Microsoft SQL Server (check ID Qsdfp3A4L1), which turns red for Standard edition instances with more than 48 vCPUs and Web edition instances with more than 32 vCPUs, and reports a recommended instance type and estimated monthly savings - Inventory SQL Server instances by edition, version and vCPU count, including BYOL instances where edition is not visible from the AMI, and compare each against its edition's cap; confirm the cap for the SQL Server version in use in Microsoft's editions documentation, since the AWS figures are based on SQL Server 2016 SP1 and later editions tables - Check whether the instance was sized for memory; Standard edition's buffer pool is also capped at 128 GB, so memory above that may not be usable either - Confirm that no other software on the instance needs the extra vCPUs before planning a resize ## How to fix 5 ways to remove the waste. - Change the instance to a size in the same family with 48 vCPUs for Standard edition or 32 vCPUs for Web edition, which is what Trusted Advisor uses to estimate savings - If the workload needs more memory relative to CPU, move to a memory-optimized family at the capped vCPU count instead of a larger general-purpose size - If the workload genuinely needs more than the edition's compute limit, evaluate whether the extra capacity is worth an edition upgrade rather than paying for vCPUs that the current edition cannot use - Stop the instance to change its type, and schedule the resize in a maintenance window; for license-included instances this keeps the same AMI and edition - Update provisioning templates so SQL Server Standard and Web instances are not launched above their edition limits ## Documentation Vendor references for pricing and configuration. - [Cost optimization - AWS Support docs.aws.amazon.com](https://docs.aws.amazon.com/awssupport/latest/user/cost-optimization-checks.html) - [Review Trusted Advisor recommendations for SQL Server workloads docs.aws.amazon.com](https://docs.aws.amazon.com/prescriptive-guidance/latest/optimize-costs-microsoft-workloads/sql-server-trusted-advisor.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-0346 ### [SQL Server Enterprise Edition on EC2 Without Enterprise Feature Use](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 chosen to avoid future limits. Many of these databases never use an Enterprise-only feature.... Databases - 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-0014 ### [Underutilized Instances in EC2 Auto Scaling Group](https://www.pointfive.co/efficiency-hub/inefficiencies/underutilized-instances-in-ec2-auto-scaling-group) Oversized instances within Auto Scaling Groups lead to inflated baseline costs, even when scaling adjusts the number of instances dynamically. When workloads consistently use only a fraction of the available CPU, memory, or network... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.