Oracle Database vs SQL Server: licensing, the Core Factor, and what each really costs

Key takeaways

• Different metrics, not directly comparable. Oracle counts processors (cores × Core Factor); SQL Server counts cores outright. You cannot compare sticker prices until you normalise to physical cores.
• List prices. Oracle Database EE: $47,500 per processor plus 22% annual support (Oracle Technology Price List, 2026). SQL Server Enterprise: roughly $7,100–$7,600 per core in 2-core packs plus ~25% Software Assurance (Microsoft list, 2026).
• The Core Factor decides everything. Most x86 cores carry a 0.5 Oracle Core Factor, so a 32-core server is 16 Oracle processors but 32 SQL Server cores.
• Virtualisation is the biggest structural gap. Oracle's partitioning policy pushes licensing to every host in a VMware cluster; SQL Server Enterprise + Software Assurance licenses per VM with mobility.
• Oracle Licensing Experts benchmark: across our engagements, re-platforming a like-for-like Oracle EE workload to SQL Server Enterprise cut three-year database licence-plus-support cost by an average of 58% — though migration effort offsets 20–40% of year-one savings (Oracle Licensing Experts benchmark, 2026).

How is Oracle Database licensed vs SQL Server?

Oracle Database is sold on one of two metrics: Processor (used for public-facing or large deployments) or Named User Plus (a counted-user metric with a minimum of 25 NUP per processor). Enterprise Edition lists at $47,500 per processor; nearly every advanced capability — Real Application Clusters, Partitioning, Multitenant, Advanced Security, the Diagnostics and Tuning Packs — is a separately licensed option layered on top.

SQL Server is sold per core under the Enterprise or Standard edition, with a four-core minimum per instance, or under a Server + CAL model (Standard only) for user-counted workloads. Unlike Oracle, the headline editions bundle most capabilities — Always On availability groups, partitioning, compression and in-memory are included in Enterprise rather than priced as add-ons.

Oracle Core Factor vs SQL Server per-core counting

This is the single most important difference for cost. Oracle multiplies the physical core count by a figure from its Core Factor Table — 0.5 for most Intel and AMD x86 cores — to derive the number of processor licences required. SQL Server applies no such multiplier: every physical core on a non-virtualised server, or every virtual core assigned to a VM, must be licensed, subject to the four-core floor.

Which is cheaper — Oracle Database or SQL Server?

For a 32-core two-socket server, Oracle EE requires 16 processor licences (32 × 0.5) — about $760,000 at list plus $167,200 a year support. SQL Server Enterprise requires 32 core licences — roughly $228,000–$243,000 at list plus around $60,000 a year Software Assurance. Even after typical discounting, SQL Server is the lower-cost commercial database on identical hardware. The gap narrows where you need Oracle-only capabilities (RAC for active-active clustering, sub-second failover, or specific workload features) and widens sharply once Oracle options stack up.

How do Oracle and SQL Server licensing differ on VMware and in the cloud?

On VMware, Oracle's Partitioning Policy is non-contractual but is the position Oracle's audit teams assert: every physical host on which an Oracle VM could ever run must be fully licensed, which on a large cluster can multiply the bill. SQL Server Enterprise with Software Assurance licenses the individual virtual machine and permits license mobility across hosts. In the public cloud, Oracle uses BYOL under Universal Credits with its own vCPU-to-licence conversion, while SQL Server relies on the Azure Hybrid Benefit — both of which require you to hold the right underlying entitlement and, for Microsoft, active Software Assurance.

When does migrating from Oracle to SQL Server make sense?

Migration pays when the workload does not depend on Oracle-specific options, when the estate is heavily virtualised (where Oracle's host-licensing rule inflates cost), or when an Oracle renewal or audit settlement creates a budget event. It rarely pays for tightly coupled applications certified only on Oracle, or where RAC-class availability is mandatory. The decision is a total-cost-of-ownership question, not a sticker-price one: factor in re-platforming effort, retraining, and the dual-run period when you model it.

Oracle Database vs SQL Server: frequently asked questions

Is SQL Server cheaper than Oracle Database?

At list, yes. Oracle Database Enterprise Edition is $47,500 per processor (Oracle Technology Price List, 2026) while SQL Server Enterprise lists at roughly $7,100–$7,600 per core (Microsoft, 2-core packs). Because Oracle applies a 0.5 Core Factor to most x86 cores and SQL Server counts every core, a 32-core server costs about 16 Oracle processors versus 32 SQL Server cores — Oracle still lands materially higher on like-for-like hardware before options.

Does SQL Server use Oracle's Core Factor Table?

No. The Core Factor Table is Oracle's own multiplier and applies only to Oracle programs. SQL Server is licensed on the physical or virtual core count with a four-core minimum per instance and no core-factor discount, so its core count maps directly to hardware.

Can I run Oracle Database on VMware without licensing every host?

Not under Oracle's standard policy. Oracle treats VMware as soft partitioning and expects every physical host a VM could run on to be licensed. SQL Server Enterprise with active Software Assurance allows per-VM licensing and license mobility, which is one of the largest structural cost gaps between the two on virtualised estates.

Do I need Software Assurance to move SQL Server licenses to the cloud?

Yes. License Mobility and the Azure Hybrid Benefit both require active Software Assurance. Without SA, SQL Server licenses cannot be reassigned to a hyperscaler. Oracle's equivalent is BYOL under the Universal Credits model, which has its own counting rules.