Why Enterprise databases are a separate budget
Proxmox VE needs no expensive hypervisor licenses — often ~90%+ savings there. But if you run Oracle EE or SQL Server Enterprise, database licensing frequently exceeds the virtualization cost itself. Both products apply strict virtualization rules — and Proxmox (KVM/QEMU) is treated by Oracle as soft partitioning, with major financial consequences.
physical cores
soft partitioning (Oracle)
before migration
Decision-makers often assume: "the VM has 4 vCPU, I pay for 4 cores." With Oracle EE and SQL Server EE on Proxmox that's usually wrong. Below — both vendors' rules and practical conclusions for a Proxmox cluster.
Oracle Database Enterprise Edition
Oracle EE is licensed against physical host cores (the Processor License model) or Named User Plus (NUP). Oracle's price list quotes Processor License units, but they are calculated from cores — not CPU sockets. In virtualization, Oracle's hard vs soft partitioning policy is decisive.
| Partitioning type | Technologies Oracle recognizes | Proxmox / KVM |
|---|---|---|
| Hard partitioning | Oracle VM Server, selected LPAR/DRP, Solaris Zones (with limits) | Not applicable |
| Soft partitioning | VMware, Hyper-V, Xen, KVM, containers without hard partitioning | Yes — Proxmox = soft |
Soft partitioning rule: on Proxmox/KVM Oracle requires licensing all physical processor cores on the server where the database runs (or could run) — regardless of vCPU assigned to the VM. Pinning a VM to a subset of cores (CPU affinity) does not, in Oracle's view, exempt the remaining host cores from licensing.
How to count core-based licenses (Processor License):
- Count all physical cores on the server (or servers, if the VM can start on multiple HA nodes).
- Multiply by the Core Processor Licensing Factor (typical Intel/AMD x86-64: 0.5).
- Round up — that's the number of Processor License units required (with factor 0.5: 1 license = 2 x86 cores).
- Minimum: 2 Processor License units per server (do not confuse with CPU socket count).
Example — 2×32-core host (64 physical cores). 64 cores × ~$23,750/core (Oracle EE, indicative) = ~$1.52M in Oracle EE licenses on one node — whether the VM has 4 or 16 vCPU.
Named User Plus can be cheaper with few users but has minimums tied to Processor License units (typically min. 25 NUP per Processor License). With many users and a large host, core-based licensing usually wins — confirm with an Oracle partner.
Add-ons (Diagnostics Pack, Tuning Pack, RAC, Active Data Guard, etc.) are separate costs under the same model — in Enterprise they often dominate the budget.
SQL Server Enterprise
SQL Server Enterprise is licensed per-core. Virtualization rules are more flexible than Oracle's but still demand care on dense Proxmox hosts.
| Model | What you license | When it makes sense on Proxmox |
|---|---|---|
| Per-core (single VM) | cores assigned to the VM (min. 4 cores per VM, min. 4 cores per physical processor) | 1–2 SQL instances on a node, few VM cores |
| Per-core (whole host) | all physical cores on the server | many SQL VMs on one node — unlimited instances |
| Enterprise + Software Assurance | per-core license with unlimited virtualization rights | dense SQL cluster, license mobility across hosts (SA terms) |
Density trap (like Windows Server): if you license the host per-core without unlimited virtualization, you pay for every physical core — even when the SQL VM has 2 vCPU (minimum 4 cores per VM). On a 128-core host with one small SQL instance, Enterprise licensing cost scales linearly with server cores.
Proxmox HA cluster: if the SQL VM can fail over to other nodes, each such node must be fully licensed (per-core host model) — unless you have Software Assurance with unlimited virtualization and meet license mobility terms. Without SA, moving core licenses between hosts is restricted (every 90 days), which conflicts with HA.
SQL Server also requires a Windows Server guest OS license — see Windows Server licensing on Proxmox VE.
Proxmox VE: HA, live migration and soft partitioning
Proxmox offers live migration, HA and Dynamic Load Balancing — but from a database licensing perspective each feature can expand the licensing scope unless you design the architecture deliberately.
- Dedicated DB nodes — carve out 1–2 hosts with fewer cores (e.g. EPYC 9175F — 16 high-frequency cores) exclusively for Oracle/SQL; keep the rest of the cluster on dense, cheaper EPYC 9755 nodes.
- Strict HA affinity — pin DB VMs with strict node-affinity to licensed nodes (HA affinity rules) so they never start on unlicensed hosts.
- Disable auto-migration for DB VMs or limit the HA node pool to fully licensed servers only.
- Pre-migration audit — verify existing Oracle/SQL licenses allow changing virtualization platform (contracts, SA, BYOL).
Hypervisor migration (VMware → Proxmox) does not automatically change Oracle or Microsoft licensing rules. It does change compliance risk — Oracle in particular often audits environments after platform changes or consolidation.
Catalog prices (indicative)
Below are indicative list prices (USD, before partner discounts). Real rates depend on enterprise agreements, channel and volume — use as a budgeting reference, not a quote.
Oracle Database Enterprise Edition
| Item | Catalog price (USD) | Approx. (PLN) |
|---|---|---|
| Oracle EE — core license (Processor License) | ~$23,750 / core | ~95,000 zł |
| Named User Plus (Oracle EE) | ~$950 / user | ~3,800 zł |
| Real Application Clusters (RAC) — add-on | ~$11,500 / core | ~46,000 zł |
| Active Data Guard — add-on | ~$11,500 / core | ~46,000 zł |
Oracle's price list quotes Processor License units (~$47,500) — a licensing unit derived from cores, not a per-CPU-socket price. With a 0.5 factor for x86-64 Intel/AMD processors, one Processor License covers 2 physical cores (~$23,750/core). The minimum is 2 Processor License units per server.
SQL Server Enterprise
| Item | Catalog price (USD) | Approx. (PLN) |
|---|---|---|
| SQL Server Enterprise — 2-core pack | ~$15,123 | ~60,500 zł |
| SQL Server Enterprise — 1 additional core | ~$7,562 | ~30,250 zł |
| Software Assurance (annual, ~25% of license) | depends on base | required e.g. for unlimited virtualization |
Example — SQL Server EE, 32-core host, 3 SQL VMs. Per-core whole-host license: 32 × ~$7,562 = ~$242,000 (~970,000 zł) — but unlimited SQL instances on the node. Three separate 8-core VMs: 3 × 8 × ~$7,562 = ~$181,000. With more instances, whole-host licensing wins.
Prices indicative (~4 zł/USD). Oracle publishes in USD; Microsoft in USD/EUR depending on channel. Cloud subscriptions (Oracle Cloud BYOL, Azure SQL, SQL on Azure VMs) use a different cost model — compare 3–5 year TCO.
Optimization strategies and recommendations
Proxmox Migracje recommendation: for nodes dedicated to enterprise databases (Oracle EE, SQL Server Enterprise) we recommend the AMD EPYC 9175F — 16 high-frequency cores with strong per-core performance and the smallest practical core count to license.
- Oracle EE on Proxmox → dedicated node with the smallest practical core count; avoid Oracle on a dense 128-core host shared with hundreds of VMs.
- SQL Server EE — many instances → license the whole host per-core (+ SA if HA mobility is needed).
- SQL Server EE — 1–2 small instances → per-VM licensing (min. 4 cores per VM).
- HA cluster → license every node the DB VM can fail over to, or use SA + unlimited virtualization (SQL) / dedicated affinity-pinned nodes (Oracle).
- Consider PostgreSQL / Oracle Standard Edition 2 where business requirements allow — TCO difference can be multiples.
Oracle and Microsoft models and prices change over time — confirm your scenario, contracts and current rates with an authorized partner. The above are general rules and indicative prices, not commercial, legal or tax advice.
Related articles: Windows Server licensing, RHEL licensing, AMD EPYC 9175F for databases.
We'll size DB licenses for your Proxmox cluster
We'll calculate required Oracle EE and SQL Server Enterprise licensing — including HA, affinity and optimal node architecture — before you approve VMware migration.
⚡ Free consultation → Windows Server licensing