Commercial Licensing Traps That Multiply Cost Faster Than Compute

Decision drivers

Oracle License Included is SE2-only; Enterprise Edition requires BYOL under the Core Factor Table (vCPU→physical-core mapping)
AWS Service Terms §10.3.1 prohibits multi-tenant/SaaS hosting under Oracle License Included — a legal constraint, not a technical one
SQL Server Enterprise HA requires Always On Availability Groups; Standard Edition is capped to Basic AGs/mirroring, restricting multi-database and secondary-read configurations
Vertical scale-up on a commercial engine multiplies license cost per core — the most common driver of "RDS got too expensive" migrations
RI instance-size flexibility does not apply to commercial engines at all, and does not apply across BYOL/License Included or across instance families even for open-source engines

Production premise

On the open-source engines, scaling compute is just a bigger instance bill. On Oracle and SQL Server, the same resize is a licensing decision wearing a compute decision's clothes.

Oracle first. License Included — where AWS holds the license — is restricted to Standard Edition 2 only. Enterprise Edition requires Bring Your Own License, priced per physical core via Oracle's Core Factor Table. A vCPU count has to be translated back to physical cores before you know what you are actually licensing: a db.m5.xlarge's 4 vCPUs map to 2 physical cores.

SQL Server splits along the same seam. Enterprise Edition HA runs on Always On Availability Groups. Standard Edition is restricted to Basic Availability Groups or mirroring, which caps you out of multi-database configurations and secondary read access — no matter how much compute you throw at it.

Failure mode & inflection point

The trap is vertical scale-up on a commercial engine. Moving from a 4-vCPU instance to a 32-vCPU instance multiplies compute cost linearly. But under BYOL it also multiplies your Oracle or SQL Server license cost by the same factor, and license cost per core is usually the larger number.

Teams that scale commercial-engine instances the way they would scale an open-source instance — reflexively, in response to load — routinely discover the problem late. By the time anyone checks, the license line has grown 5–10x faster than the infrastructure line.

License Included on Oracle carries a separate hosting restriction. AWS Service Terms §10.3.1 prohibits using License Included Oracle to host multi-tenant third-party SaaS or external services. A product built on it can later pivot toward hosting other companies' workloads, and the constraint then shows up as a compliance problem, not a performance one.

Production guardrail

Default to open-source engines — PostgreSQL or MySQL — unless a specific application dependency requires Oracle or SQL Server. For new production workloads without an existing dependency, the licensing model alone is reason enough to avoid the commercial engines.

Where a commercial engine is already required, use License Included only for genuinely internal, single-tenant workloads, on Oracle SE2 or SQL Server Standard/Enterprise. Treat any BYOL Enterprise Edition scale-up as a licensing review first and an instance-class change second: get the per-core cost confirmed before resizing. If the workload will ever host external tenants' data or serve as a multi-tenant SaaS backend, License Included Oracle is disqualified outright by §10.3.1. Make that decision before building on it.