Resizing the Azure VM from E4ads_v5 (4 vCPUs) to E8ads_v5 (8 vCPUs) increases the number of vCPUs, so additional SQL Server Standard core licenses are required if SQL Server is licensed per core.
Key points:
- For pay-as-you-go SQL images on Azure VMs, the SQL Server license cost is tied to the number of VM vCPUs. When the VM is resized to more vCPUs, the per‑second SQL licensing charge increases automatically based on the new vCPU count. No separate purchase is needed, but the bill will be higher because of more cores.
- For Azure Hybrid Benefit or bring‑your‑own‑license scenarios, SQL Server per‑core licensing must cover all vCPUs that SQL Server can see. If the VM is resized from 4 to 8 vCPUs, the licensed core count must be increased accordingly, or the vCPUs available to SQL Server must be constrained to match the existing licensed cores.
- Configurable Constrained Cores (CCC) can be used to keep SQL licensing aligned with an existing core entitlement while still gaining more memory and I/O from a larger VM size. In that case,
vCPUsAvailable is set to the licensed core count so SQL Server only sees that number of logical processors.
So, if SQL Server Standard is licensed per core and the VM is resized to 8 vCPUs without constraining cores, additional SQL Server 2019 Standard core licenses are required to remain compliant.
References: