A buyer side guide to choosing between Oracle Database Enterprise Edition and Standard Edition 2 in 2026. The feature split, the socket cap, the metrics, and the cost.
Enterprise Edition is the full feature database, licensed per processor after the core factor, with no hardware ceiling. Standard Edition 2 is far cheaper, licensed per occupied socket, and capped at two sockets and sixteen threads.
Quick answer
Where Standard Edition 2 is legal to run, it is almost always the cheaper edition. The crossover is not a price point. It is the moment you cross a cap, need a gated feature, or need two nodes serving at once.
This guide is for database and procurement leaders choosing an Oracle Database edition in 2026. Read it with the SE2 versus Enterprise guide and the Oracle Practice page so the technical fit and the license fit stay aligned.
The split is feature scope and hardware ceiling, not engine quality. Both editions ship the same binary, the same optimizer, and the same SQL. Enterprise Edition unlocks capability and removes the ceiling.
The priced options live in Enterprise Edition only, and so do several capabilities that are not options at all. If your workload needs one of them, Standard Edition 2 is out regardless of size.
Standard Edition 2 runs only on servers with at most two occupied sockets, and each SE2 database is capped at sixteen CPU threads. Above either line, Enterprise Edition is the only legal answer.
The socket rule counts occupied sockets on the physical server. A virtual machine that presents two sockets on a four socket host does not qualify the host.
SE2 is not a reduced engine. It keeps the full SQL and PL/SQL stack, RMAN, basic table compression, up to three pluggable databases, and Standard Edition High Availability for active passive failover at no extra fee.
The dividing line is entitlement, not performance. Standard Edition 2 ships a complete relational engine, but the priced options and most high availability features are switched off.
The table shows where each capability lands, with the Enterprise only options priced per processor on Oracle's price list.
Two limits do the heavy lifting. The sixteen thread cap constrains how much CPU a single SE2 instance can consume even on a legal two socket box, and the removal of RAC from 19c means clustering is now an Enterprise Edition path.
If any row above is a hard requirement, the edition decision is already made and the rest of this page is arithmetic you do not need.
Enterprise Edition uses processor licensing with the core factor, or Named User Plus with a 25 per processor minimum. Standard Edition 2 uses occupied sockets, or Named User Plus with a 10 per server minimum.
Oracle Database editions compared
| Dimension | Standard Edition 2 | Enterprise Edition |
|---|---|---|
| License metric | Per occupied socket or Named User Plus | Per processor or Named User Plus |
| Core factor applied | No | Yes, from the published table |
| User minimum | 10 per server | 25 per processor |
| Hardware cap | Two occupied sockets | None |
| Priced options | Not available at any price | Full option catalog |
| Annual support | 22 percent of net license fee | 22 percent of net license fee |
Enterprise Edition applies a core factor to physical cores to set the processor count. Current Intel Xeon and AMD EPYC chips carry 0.5, so 32 cores equal 16 processors, while IBM POWER carries 1.0 and doubles the same box.
Oracle publishes the licensing basics that define these metrics, and the multipliers themselves sit in the core factor table. The worked counting is on our Oracle core factor page.
Named User Plus helps only when the user population is small and the server is small with it. The minimum is calculated from the processor count, so a large server drags the floor up with it.
White Paper · Oracle Database
Oracle Standard Edition Two Licensing
Where SE2 wins, and the caps that bite. Read it free.
The list prices sit far apart and the two metrics scale in opposite directions, so the gap widens as servers get denser. SE2 is priced per occupied socket at $17,500 before discount, and Enterprise Edition per processor at $47,500 before discount.
Take the largest server Standard Edition 2 permits, two sockets. Licensed for SE2 that is 2 x $17,500 = $35,000 at list.
Put Enterprise Edition on the same box with two sixteen core CPUs and the arithmetic inverts. 32 cores x 0.5 = 16 processors, and 16 x $47,500 = $760,000 at list, before a single option is added.
The same two socket server as core density rises
| Cores per socket | EE processors | EE license at list | SE2 license at list | Ratio |
|---|---|---|---|---|
| 8 | 8 | $380,000 | $35,000 | 11 times |
| 16 | 16 | $760,000 | $35,000 | 22 times |
| 32 | 32 | $1,520,000 | $35,000 | 43 times |
| 64 | 64 | $3,040,000 | $35,000 | 87 times |
List, before discount, core factor 0.5. SE2 would use only sixteen threads of any of these servers, which is the trade you are actually making.
Because SE2 ignores core count entirely, its value per core improves as density rises, while Enterprise Edition cost climbs with every core. There is effectively no core count at which Enterprise Edition beats SE2 on price where SE2 is legal to run.
Options compound the gap. A database on Enterprise Edition with Partitioning, Diagnostics and Tuning is $47,500 + $11,500 + $7,500 + $5,000 = $71,500 per processor at list, before discount.
For the full SE2 rulebook see our Oracle Standard Edition 2 licensing guide. Treat every discount quoted here as an observed range from our own deal file, negotiated case by case.
The crossover is not a price. It is a set of four thresholds, and crossing any one of them moves you to Enterprise Edition whatever the arithmetic says.
Price the four before you buy hardware, because three of them are decided by choices made outside the database team.
What each crossover costs on a typical two socket, 32 core server
| Threshold | What triggers it | Cost of crossing, at list |
|---|---|---|
| The third occupied socket | A hardware refresh onto a four socket chassis | Whole server relicenses to EE. On 64 cores that is 32 processors, $1,520,000 |
| Sustained demand above sixteen threads | Batch or reporting growth the instance cannot absorb | EE on the same box, 16 processors, $760,000, plus the tuning options you will then want |
| The first gated feature | A compliance program asking for encryption, or a vendor requiring Partitioning | EE base plus the option. Partitioning adds $11,500 per processor, Advanced Security $15,000 |
| Two nodes serving one database | An availability requirement that failover does not meet | EE plus RAC at $70,500 per processor, doubled across the pair |
Every one of these is cheaper to plan for than to discover. Two of them are usually decided by an infrastructure refresh nobody told the license owner about.
There is one honest case, and it is a consolidation case rather than a per server case. If a single Enterprise Edition server can replace a large number of SE2 servers, the license lines can meet.
The break point is roughly forty three two socket SE2 servers. That is $1,505,000 of SE2 licenses against a two socket, 32 core Enterprise Edition box at $1,520,000 with no options.
In practice that consolidation is impossible without the options you are trying not to buy, and forty three departmental databases will not fit inside sixteen threads on one box. The theoretical crossover exists. We have never seen a client reach it.
The realistic end state is a split estate, not a single edition. Keep Enterprise Edition where a named feature is genuinely in production, and move everything else.
You relicense the whole server to Enterprise Edition, and the SE2 licenses you already own do not automatically carry across. That is the expensive failure mode, and it is entirely avoidable at purchase time.
Take a departmental system bought on SE2 in year one, on a two socket, 16 core box, for $35,000 plus $7,700 of support. In year three the business doubles and the refresh lands on a four socket, 64 core chassis.
The same event handled at purchase time looks completely different, because you have a written trade up price and a hardware standard that keeps you inside two sockets.
Match the edition to the workload, not to habit. The cheapest compliant edition is the goal, and Standard Edition 2 is the one most often left on the table.
The risk is using Enterprise options without licensing them. Features enabled by default or by a DBA create exposure that an audit converts into a back bill, priced on the whole server rather than the database.
Oracle's Standard Edition 2 page sets the socket and thread ceiling, while the Database Licensing manual lists which options are Enterprise Edition only.
The Technology Price List fixes the per processor and per Named User Plus rates, and the core factor table governs Enterprise Edition processor counts. Those four documents settle nearly every internal edition argument.
The standard advice is to default new databases to Enterprise Edition so you never hit a feature wall. We disagree. In the edition reviews Fredrik Filipsson ran across 2024 and 2025, roughly four in ten Enterprise Edition databases used no Enterprise only feature at all, and the premium bought nothing but a feeling. The buyer side move is to inventory the actual features in use per database, map each to the lowest edition that supports it, and migrate the eligible workloads to Standard Edition 2 before the next renewal. Default to Enterprise Edition only where a named Enterprise feature is genuinely in production, not as a precaution against a wall you may never reach. Headroom is not free, and on a 32 core box it lists at $1,485,000 more than the alternative.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Enterprise Edition is rarely the cheaper choice. It is the mandatory choice, and the only question worth arguing is whether anything in your estate has actually made it mandatory.
Work the list in order. The first four steps cost nothing and produce the map that every later conversation depends on.
Enterprise Edition is the full feature database licensed per processor after the core factor, with no hardware cap. Standard Edition 2 is a lower cost edition licensed per occupied socket, capped at two sockets and sixteen threads, with the priced options switched off. Both run the same engine and the same SQL.
Standard Edition 2 is licensed per occupied socket on servers with a maximum of two sockets, at $17,500 per socket, or by Named User Plus at $350 with a minimum of ten users per server. It cannot run on servers above the socket limit at all, which caps the hardware it supports.
Enterprise Edition is licensed per processor at $47,500, applying the Oracle core factor to physical cores, or by Named User Plus at $950 with a minimum of 25 users per processor. It carries no socket or thread cap, so it scales to large servers and clustered estates.
Yes, by a wide margin, and the margin grows with core density. On a two socket server with 32 cores the list gap is $35,000 against $760,000. The catch is the socket cap and the missing options, so the saving only holds where the workload fits inside the SE2 limits.
There is no realistic price crossover where SE2 is legal to run. The crossover is capability based, and it happens at one of four thresholds: a third occupied socket, sustained demand above sixteen threads, the first gated feature, or a requirement for two nodes serving one database at once.
No, and they cannot be bought for SE2 at any price. Partitioning, Advanced Compression, Advanced Security, Active Data Guard, and the Diagnostics and Tuning Packs all require Enterprise Edition. Using one on SE2 is both technically blocked and a compliance exposure if a workaround is attempted.
The whole server has to be relicensed to Enterprise Edition, counted on every core after the core factor. The SE2 licenses you already own do not convert automatically, and any credit is a negotiated trade up rather than a contractual right. Ask for that trade up price in writing before you buy SE2.
Match the edition to workload size and feature need, evidenced rather than assumed. If the database fits the socket and thread limits and needs no Enterprise option, Standard Edition 2 saves heavily. If it needs scale, options, or clustering beyond the cap, Enterprise Edition is required.
Enterprise Edition is $47,500 per processor on Oracle's price list before discount, where a processor equals physical cores multiplied by the 0.5 core factor for current x86 chips. Standard Edition 2 is $17,500 per occupied socket by comparison. Priced options such as Partitioning or Advanced Security add further fees per processor on top of the Enterprise base license.
Not where Standard Edition 2 is legal to run. SE2 is priced per socket regardless of core count, while Enterprise Edition is priced per core after the core factor, so Enterprise Edition costs more at any real server size. It becomes the required choice when you exceed a cap or need a gated option.
The socket and vCPU caps, where SE2 beats Enterprise Edition, and the cloud rules that change the cap.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Enterprise Edition is bought where Standard Edition 2 would fit, and options are switched on without a license. Both surface in any audit.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One short note on Oracle Database editions, licensing metrics, option compliance, and the buyer side moves we are running in client engagements.
