Contents
Key takeawaysHow the editions differFeatures gated to Enterprise EditionHow each edition is licensedWhat each edition costsThe real crossoverWhat our reviews foundOutgrowing SE2 mid termChecking your own positionWhat Oracle will sayWhat to do nextFAQStandard Edition 2 is far cheaper wherever it is allowed: $17,500 per occupied socket against $47,500 per Enterprise Edition processor. Price rarely decides the edition. A third socket, sixteen threads, a gated feature or a second active node does.
- Two different metrics. Enterprise Edition lists at $47,500 per processor after the core factor, while Standard Edition 2 lists at $17,500 per occupied socket and ignores cores entirely.
- The gap grows with density. On the same two socket, 32 core server, Enterprise Edition lists at $760,000 against $35,000 for SE2, and every added core widens the difference.
- Capability decides the edition. Four events force Enterprise Edition: a third occupied socket, sustained demand above sixteen threads, a gated feature, or two nodes serving one database.
- Named User Plus rarely rescues Enterprise Edition. The 25 per processor minimum means 400 users on a 16 processor server, whatever your real headcount.
- Outgrowing SE2 is the expensive failure. SE2 licenses do not convert automatically, so a four socket refresh relicenses the whole server unless a trade up price was agreed in writing.
- Many Enterprise Edition databases do not need it. In our 2024 and 2025 reviews, 40 to 50 percent used nothing that SE2 could not cover, and the feature usage view shows which ones.
This guide is for database and procurement leaders choosing an Oracle Database edition in 2026, or checking whether the editions they already run still fit. Read it with the Oracle Practice page so the technical fit and the license fit stay aligned.
What separates Oracle Database Enterprise Edition from Standard Edition 2?
Two things separate them: the features you are entitled to use and the hardware you may run on. Both editions ship the same binary, the same optimizer and the same SQL, so the engine itself is identical. Enterprise Edition adds capability and removes the hardware ceiling.
Which features need Enterprise Edition?
Every priced option runs on Enterprise Edition only, including Partitioning, Advanced Security for Transparent Data Encryption and redaction, and Active Data Guard. Several features with no separate fee are Enterprise only too: Data Guard itself, parallel query, bitmap indexes, online index rebuild and basic table compression.
If a workload needs any one of them, SE2 is out however small the workload is. The next section lists each gated capability with its option price.
What is the hardware ceiling for Standard Edition 2?
Standard Edition 2 may run 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 choice.
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. The database enforces the thread cap itself, so a busy SE2 instance queues for CPU once it reaches sixteen threads.
What does Standard Edition 2 keep?
SE2 is a complete relational engine. It keeps the full SQL and PL/SQL stack, RMAN backup and recovery, up to three pluggable databases per container, and Standard Edition High Availability for active passive failover at no extra fee. What it lacks is the option catalog and the included Enterprise Edition features listed above.
How to Negotiate Your Oracle SaaS Renewal: The Five Moves at the Table
Which Oracle Database features are gated to Enterprise Edition?
All priced options, Data Guard and several included performance features are Enterprise Edition only, and Real Application Clusters has been Enterprise only since 19c. The table shows where each capability lands, with the options at their per processor list price.
| Capability | Standard Edition 2 | Enterprise Edition |
|---|---|---|
| Real Application Clusters | Removed from 19c onward, single instance only | Priced option, $23,000 per processor |
| Standard Edition High Availability | Included from 19c Release Update 19.7 | Not applicable |
| Partitioning | Not available | Priced option at $11,500 per processor |
| Data Guard, basic standby | Not available | Included |
| Active Data Guard, read access on the standby | Not available | Priced option, $11,500 per processor, on top of Data Guard |
| Transparent Data Encryption, Advanced Security | Not available | Priced option, $15,000 per processor |
| Advanced Compression, beyond basic compression | Not available | Priced option, $11,500 per processor |
| Basic table compression | Not available | Included |
| Database In-Memory | Not available | Priced option, $23,000 per processor |
| Diagnostics and Tuning Packs | Not available | Priced options, $7,500 plus $5,000 per processor |
| Parallel query, bitmap indexes, online index rebuild, query rewrite | Not available | Included |
| Hardware ceiling | Two sockets maximum, sixteen CPU threads per database | No socket or thread cap |
Two limits do most of the work. The sixteen thread cap constrains how much CPU one SE2 instance can use even on a legal two socket box. With RAC gone from SE2 since 19c, clustering is now an Enterprise Edition path.
If any row above is a hard requirement for a workload, its edition is already decided. The cost comparison in the rest of this page only matters for the workloads that remain.
Oracle Standard Edition Two Licensing
Where SE2 wins, and the caps that limit it.
Get the white paper →How is each Oracle Database edition licensed?
Enterprise Edition is licensed per processor, with the core factor applied to physical cores, or by Named User Plus with a minimum of 25 users per processor. Standard Edition 2 is licensed per occupied socket, or by Named User Plus with a minimum of 10 users per server.
| Dimension | Standard Edition 2 | Enterprise Edition |
|---|---|---|
| License metric | Per occupied socket or Named User Plus | Per processor or Named User Plus |
| List price | $17,500 per socket, $350 per user | $47,500 per processor, $950 per user |
| 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, $3,850 per socket at list | 22 percent of net license fee, $10,450 per processor at list |
How does the core factor work?
Enterprise Edition multiplies physical cores by a core factor to set the processor count. Current Intel Xeon and AMD EPYC chips carry 0.5, so 32 cores equal 16 processors. IBM POWER carries 1.0, which doubles the count for the same number of cores.
Oracle's licensing basics document defines the metrics, and the multipliers sit in the core factor table. We walk through the counting, rounding included, on our Oracle core factor page. SE2 ignores the table: one occupied socket is one license whatever the core count.
When does Named User Plus make sense?
Named User Plus helps only when the user population is small and the server is small too. The minimum is calculated from the processor count, so a large server raises the floor with it.
- Enterprise Edition on 16 processors. The minimum is 400 users at $950, so $380,000 at list whether you have 40 users or 400.
- Enterprise Edition on 4 processors. On a server with 8 x86 cores the floor is 100 users, or $95,000, against $190,000 in processor licenses. With fewer than 200 users, Named User Plus is the cheaper metric here.
- Standard Edition 2 on one server. The minimum is 10 users at $350, so $3,500 at list, against $35,000 for two sockets. Sixty users would cost $21,000.
- The SE2 flip point. Above roughly 100 users on a two socket server, socket licensing is cheaper and ends any dispute over who counts as a user.
- Devices count as users. Scanners, sensors and service accounts each need a Named User Plus license, and so does every person behind a shared application login.
How do the editions count in AWS, Azure and Google Cloud?
In Oracle's authorized cloud environments (AWS, Microsoft Azure and Google Cloud) vCPUs replace cores and sockets, and the core factor table does not apply. For Enterprise Edition, two vCPUs count as one processor license when multithreading is enabled.
- Sockets become vCPUs. For SE2, every four vCPUs count as one socket, rounded up.
- The cap becomes eight vCPUs. SE2 may only be licensed on instances of up to eight vCPUs, so an 8 vCPU instance needs two SE2 socket licenses, $35,000 at list, against four Enterprise Edition processor licenses at $190,000.
- Larger instances are Enterprise Edition only. A 16 vCPU instance needs 8 processor licenses.
- The user floor changes too. The SE2 Named User Plus minimum in these clouds is 10 users per 8 vCPUs.
Oracle Cloud Infrastructure counts differently; see Oracle Database licensing in cloud environments. Our white paper on Oracle Standard Edition Two licensing sets out where SE2 wins and which caps limit it.
What does Enterprise Edition cost compared with Standard Edition 2?
At list, Standard Edition 2 costs $17,500 per occupied socket and Enterprise Edition $47,500 per processor, both before discount. The two metrics scale in opposite directions, so the gap widens as servers get denser.
Take the largest server SE2 permits, two sockets. Licensed for SE2 that is 2 x $17,500 = $35,000. Put Enterprise Edition on the same box with two sixteen core CPUs and 32 cores x 0.5 = 16 processors, so 16 x $47,500 = $760,000 before a single option is added.
| 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 |
Because SE2 ignores core count, its value per core improves with every generation of denser chips, while Enterprise Edition cost climbs with each added core. Where SE2 is legal to run, there is no core count at which Enterprise Edition wins on price.
The trade you make with SE2 is capacity. The 32 core server in the second row offers 64 threads with multithreading on, and one SE2 database will use 16 of them.
What do Enterprise Edition options add?
Options are priced per processor on the same count as the base license, so they multiply the gap. A database with Partitioning, the Diagnostics Pack and the Tuning Pack costs $47,500 + $11,500 + $7,500 + $5,000 = $71,500 per processor at list. On 16 processors that is $1,144,000.
Worked example: five years on one server
Say you run one two socket server with 16 cores per socket and plan to keep it five years. The table uses list prices and five years of support at 22 percent, held flat for simplicity, although Oracle normally raises support each year.
| Edition and options | License | Annual support | Five years of support | Five year total |
|---|---|---|---|---|
| SE2, two sockets | $35,000 | $7,700 | $38,500 | $73,500 |
| EE, 16 processors | $760,000 | $167,200 | $836,000 | $1,596,000 |
| EE with Partitioning, Diagnostics and Tuning | $1,144,000 | $251,680 | $1,258,400 | $2,402,400 |
Discounts are negotiated case by case and apply to both editions, so they shrink the absolute gap without closing it. For the full set of SE2 rules, see our Oracle Standard Edition 2 licensing guide.
Where is the real crossover between SE2 and Enterprise Edition?
The crossover is a set of four thresholds, and crossing any one of them puts a workload on Enterprise Edition whatever the price comparison says. Price all four before you buy hardware, because three of them are decided by people outside the database team.
Which four thresholds end the SE2 case?
| Threshold | What triggers it | Cost of crossing, at list |
|---|---|---|
| The third occupied socket | A hardware refresh onto a four socket chassis | The 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 an application vendor requiring Partitioning | EE base plus the option. Partitioning adds $11,500 per processor, or $184,000 on 16 processors; Advanced Security adds $15,000 per processor |
| 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: $2,256,000 for two 16 processor nodes |
Each of these is cheaper to plan for than to discover. The third socket and the thread ceiling usually arrive through an infrastructure refresh that the license owner hears about after the hardware is ordered.
Is there any case where Enterprise Edition costs less?
It can, through consolidation: when one Enterprise Edition server replaces many SE2 servers, the license totals can meet. The break point is roughly 43 two socket SE2 servers: $1,505,000 of SE2 licenses against $1,520,000 for one Enterprise Edition server with two 32 core sockets and no options.
In practice that consolidation needs the options you are trying not to buy, and 43 departmental databases on one host create capacity and availability problems of their own. We have never seen a client reach this point.
Why do most organizations end up running both editions?
Most organizations that run the numbers end up with a split deployment. They keep Enterprise Edition where a named feature is in production and move everything else to SE2.
- Map feature use per database. One query per database and an afternoon of work produce the map, and the map is what you negotiate with.
- Group by server, not by database. Edition is a server level decision, so one Enterprise Edition database on a host keeps the whole host on Enterprise Edition.
- Consolidate the Enterprise Edition remainder. Run fewer, denser Enterprise Edition servers and license each option on as few hosts as possible.
- Check the support set boundaries. If the licenses you retire share a support set with licenses that stay, Oracle's repricing clause can absorb the saving.
What have we seen in recent Oracle edition reviews?
Across roughly 35 to 45 Oracle Database edition reviews we ran in 2024 and 2025, a large share of Enterprise Edition deployments did not use a single Enterprise only feature. The same four findings came up again and again.
- Around 40 to 50 percent of Enterprise Edition databases used no option or feature that Standard Edition 2 could not cover.
- SE2 socket and thread limits were misread, so eligible workloads stayed on Enterprise Edition by default.
- Where a buyer had outgrown SE2, no one had priced the trade up in advance, so the negotiation opened as a compliance problem.
- Moving an eligible workload to SE2 cut license and support cost by 50 to 70 percent per database.
In round numbers that was about 40 reviews, with about 45 percent of Enterprise Edition databases eligible for SE2 and a median cost reduction of about 60 percent where they moved. Expect a business case to land well below the list ratios in the density table: net prices, support already paid and migration effort all narrow it.
Why we advise against putting every new database on Enterprise Edition
The common advice is to default new databases to Enterprise Edition so the team never hits a feature wall. We disagree, because the reviews above found a large share of Enterprise Edition databases using no Enterprise only feature at all. For those databases the premium bought nothing the business used.
The better course is to list the features each database uses, map each to the lowest edition that supports it, and migrate eligible workloads to SE2 before the next renewal. Reserve Enterprise Edition for databases using its features today.
Headroom bought in advance is expensive. On a two socket server with 32 cores per socket, Enterprise Edition lists at $1,485,000 more than SE2.
Enterprise Edition is rarely the cheaper choice. It is sometimes the required one, and the question worth arguing is whether anything in your environment has made it required.
What happens if you outgrow SE2 mid term?
You relicense the whole server to Enterprise Edition, and the SE2 licenses you already own do not carry across automatically. It is the most expensive failure in edition planning, and you can avoid it at purchase time.
What does outgrowing SE2 cost?
Take a departmental system bought on SE2 in year one, on a two socket, 16 core box, for $35,000 plus $7,700 a year of support. In year three the business doubles and the refresh lands on a four socket, 64 core chassis.
- The new box is Enterprise Edition only. Four occupied sockets put SE2 out of scope regardless of how the workload behaves.
- The count is 32 processors. 64 cores at a 0.5 core factor come to $1,520,000 at list before any discount.
- The SE2 spend is stranded. Any credit toward Enterprise Edition is a negotiated trade up, not a contractual right.
- The negotiating position is weak. You are buying under a deadline, on hardware already ordered, which is the worst moment to ask for a discount.
Handled at purchase time, the same event looks very different, because you hold a written trade up price and a hardware standard that keeps you inside two sockets.
How do you buy SE2 so growth does not punish you?
- Standardize on two socket hardware. Write it into the infrastructure standard so a refresh cannot break the license without anyone noticing.
- Get the trade up priced in writing. Ask for the Enterprise Edition migration price when you buy SE2, while Oracle still wants the deal.
- Buy cores per socket. Two sockets of high core count chips cost the same in SE2 as two sockets of small ones, so take the headroom at no license cost.
- Watch the thread ceiling. Track sustained CPU use against sixteen threads and treat 80 percent as the trigger to plan.
- Review before every hardware refresh. A hardware refresh is the usual way SE2 eligibility breaks.
Which contract terms should you ask for?
- A written trade up price. State the Enterprise Edition per processor price, and any credit for SE2 fees already paid, for a named period. Without it, the credit is whatever Oracle offers on the day.
- Price holds on likely options. If Partitioning or the Diagnostics Pack is a probable next step, fix its discount in the current order so it is not quoted later at a lower discount than the base license.
- A support repricing statement. Ask how support on retained licenses will be calculated if you terminate the Enterprise Edition licenses you move off. This one answer decides whether the migration saves money.
- A migration window. Request written permission to run the old and new deployments side by side while the data migrates, so the overlap is not treated as extra use.
How do you check which edition and features you actually run?
Query each database for its edition and feature history, and read socket and core counts from the physical host. Purchase records only show what was bought. Oracle's audit team reads the same views, so your numbers should match theirs before anyone asks.
Which views and scripts show edition and feature use?
- V$VERSION. The banner names the installed edition for each database.
- DBA_FEATURE_USAGE_STATISTICS. Records which features each database has used, with a detected usage count and first and last usage dates.
- options_packs_usage_statistics.sql. Oracle's script on My Oracle Support maps that view to the licensable options and packs, which is the version an auditor recognizes.
- CONTROL_MANAGEMENT_PACK_ACCESS. This parameter defaults to DIAGNOSTIC+TUNING on Enterprise Edition. Set it to NONE wherever you have not bought the packs.
- lscpu on the physical host. Reports sockets and cores per socket. For a virtual machine, read the host, never the guest.
- resmgr:cpu quantum waits. Sustained waits on an SE2 database show the sixteen thread cap is being reached.
For how Oracle's own collection tools report these results, see our note on interpreting Oracle database script output.
Where is the compliance risk?
The risk is using Enterprise Edition options without licensing them. Features enabled by default or by a DBA create exposure that an audit turns into a back bill, priced on the whole server's processor count.
- Confirm the fit. Check whether the workload sits inside the two socket and sixteen thread limits.
- List the options. Establish which Enterprise features are actually used, evidenced from the feature usage view.
- Pick the cheapest compliant edition. Usually that is SE2 where it fits, and Enterprise Edition only where a named feature is in production.
What does moving a database from Enterprise Edition to SE2 involve?
You cannot convert an Enterprise Edition database to SE2 in place. The supported route is a logical migration, usually a Data Pump export and import into a new SE2 database. The opposite direction is simpler, because Enterprise Edition software can open an existing SE2 database.
Plan for the features SE2 will not accept. Data Pump's PARTITION_OPTIONS=MERGE setting folds partitioned tables into ordinary ones, and bitmap indexes must be dropped or rebuilt as B tree indexes. Maintenance jobs that relied on online index rebuild or parallel query need rewriting, and that work usually sets the project timeline.
What does Oracle publish on the two editions?
Four Oracle documents settle most internal arguments about editions. The Standard Edition 2 FAQ sets the two socket limit and confirms that RAC left SE2 in 19c, and the Database Licensing manual lists which features and options are Enterprise Edition only.
The Technology Price List fixes the per processor and Named User Plus rates, and the core factor table governs Enterprise Edition processor counts. Save a dated copy of each with every order, because Oracle revises them from time to time.
What will the Oracle account team say, and how should you answer?
Expect resistance when you propose moving workloads to SE2, because each migration reduces Oracle's support revenue. These are the lines we hear most often, with replies that hold up.
- "SE2 is not meant for production systems." Answer that it is the same engine with the same SQL, and that Standard Edition High Availability covers local failover. Then ask which specific feature the workload lacks.
- "You will need Data Guard for disaster recovery." Set the recovery point and recovery time targets first. SE2 can feed a manually managed standby from archived redo logs, and the standby server needs its own SE2 licenses.
- "Terminating Enterprise Edition licenses will reprice your support." Ask for the calculation in writing before you commit. It decides which licenses to terminate and which to keep.
- "We can discount Enterprise Edition heavily instead." Compare the discounted Enterprise Edition price with SE2 at its own net price. On a 32 core server the list gap is 22 times, which no discount closes.
- "A trade up credit will be available when you need it." Ask for it in the ordering document. A promise from the current account manager does not bind the next one.
For how the Enterprise Edition option catalog is priced and audited, see our guide to Enterprise Edition options pricing.
What to do next
- Inventory. List each database by edition, occupied sockets on the host and options in use.
- Test the fit. Confirm whether each workload sits inside the two socket and sixteen thread limits.
- Close unlicensed use. Check the feature usage view for Enterprise options enabled without a license, then disable or license each one and record the date.
- Model five years. Compare SE2 and Enterprise Edition for every database that fits, support included.
- Price the thresholds. Cost the four crossover events for each SE2 candidate so growth does not surprise you in year three.
- Get the trade up in writing. Ask Oracle for the Enterprise Edition price before you buy any SE2 licenses.
- Check the support set. Confirm the licenses you plan to retire can leave without repricing the ones that stay.
- Negotiate from the map. Take the edition map into your next Oracle negotiation or ULA review, alongside our Oracle Database licensing guide.
Want a second opinion on your Oracle position? Our Oracle licensing consultants are former Oracle insiders who now work only for buyers.
Frequently asked questions
What is the difference between Oracle Database Enterprise Edition and Standard Edition 2?
Both run the same engine and the same SQL. Enterprise Edition adds the priced options, Data Guard, parallel query and unlimited hardware, and is licensed per processor after the core factor. Standard Edition 2 is licensed per occupied socket and limited to two sockets and sixteen threads per database, which suits departmental and midsize systems.
How is Oracle Standard Edition 2 licensed?
At $17,500 per occupied socket on servers with at most two sockets, or $350 per Named User Plus with a floor of ten users per server. SE2 cannot be installed on a larger server at any price. In AWS, Azure and Google Cloud, four vCPUs count as one socket and instances are limited to eight vCPUs.
How is Oracle Enterprise Edition licensed?
At $47,500 per processor, where processors are physical cores multiplied by the core factor, or $950 per Named User Plus with 25 users per processor as the floor. It has no socket or thread limit, so it scales to large servers and clusters, and every option you add is licensed on the same processor count.
Is Oracle Standard Edition 2 cheaper than Enterprise Edition?
Yes, wherever the workload fits, and by more as chips gain cores. Check the fit before you count the saving: one required feature such as Partitioning or Transparent Data Encryption puts that server on Enterprise Edition, and the saving on it disappears.
Where is the crossover point between SE2 and Enterprise Edition?
Price never forces the switch where SE2 is legal. Capability does, at one of four points: a third occupied socket, sustained load above sixteen threads, the first Enterprise only feature, or two nodes serving one database at once. Map which of these each system could reach within its hardware life as well as today.
Can you use options like Partitioning on Standard Edition 2?
No. Oracle does not sell Partitioning, Advanced Compression, Advanced Security, Active Data Guard or the Diagnostics and Tuning Packs for SE2. The SE2 software blocks them, and a workaround such as running Enterprise Edition binaries against a database licensed as SE2 turns a technical limit into an audit finding.
What happens if a server grows past two sockets?
SE2 is no longer permitted on it, and the whole server needs Enterprise Edition licenses on every core after the core factor. Oracle treats any credit for the SE2 licenses as a commercial concession. A trade up price written into the original SE2 order is the only protection you can secure in advance.
How do buyers choose between the two editions?
Start from evidence: the feature usage view, the host socket count and peak CPU use per database. Put each database on the cheapest edition that covers what it uses, then group by host, since one Enterprise Edition database on a server puts every database on that server on Enterprise Edition.
How much does Oracle Database Enterprise Edition cost per processor?
$47,500 at list, plus $10,450 a year of support. On current x86 chips a processor license covers two physical cores. Options add their own per processor fees on the same count, such as $5,000 for the Tuning Pack and $23,000 each for Real Application Clusters and Database In-Memory.
Does Enterprise Edition ever cost less than Standard Edition 2?
Only in a theoretical consolidation, where one large Enterprise Edition host replaces about 43 two socket SE2 servers. Compared server by server, SE2 costs less at any core count where it is allowed. Enterprise Edition becomes necessary once a cap or a gated feature applies, and that is a capability decision.