Contents
Key takeawaysThe four SE2 rulesSE2 against Enterprise EditionSeveral databases on one serverHow the edition has changedWhere audit findings come fromNamed User Plus on SE2SE2 in AWS, Azure and GoogleWhat our reviews showedWhat Oracle will sayWhat to do nextFAQOracle Standard Edition 2 licenses each occupied socket on servers with two socket capacity and ignores cores entirely. For databases that fit its four rules it costs a fraction of Enterprise Edition, and the gap grows with every hardware refresh.
- Four rules define the edition. Two socket capacity, one license per occupied socket, 16 CPU threads per database and a floor of 10 Named User Plus per server.
- Socket capacity decides eligibility. A four socket server can never run SE2, however many of its sockets stay empty.
- Cores are ignored. A 16 core chip and a 64 core chip in the same socket each need one SE2 Processor license, so denser hardware costs the same.
- One box, many databases. Because the thread cap applies per database, a single legal two socket server can host a dozen SE2 databases on two Processor licenses.
- Model support repricing first. Enterprise Edition and SE2 sit in the same license set, so terminating part of an order reprices support on what remains.
- Matching the edition pays. Buyers who chose the edition by the actual rules cut database license and support cost by 25 to 45 percent.
What are the Oracle Standard Edition 2 licensing rules?
Four rules define SE2. The server must have a maximum capacity of two sockets, you buy one Processor license per occupied socket, each database is capped at 16 CPU threads, and Named User Plus has a floor of 10 users per server.
Only the thread ceiling is about performance. The other three decide whether you may run SE2 at all and how much you owe, so those three are where both the savings and the audit findings come from.
| Rule | The wording that matters | What it controls |
|---|---|---|
| Socket capacity | Maximum capacity of two sockets on the server | Whether you may run SE2 on that box at all |
| License count | One Processor license per occupied socket | Whether you owe one license or two |
| Thread ceiling | 16 CPU threads of user execution per database | How fast one database can go, never what you owe |
| User floor | Minimum 10 Named User Plus per server | The cheapest legal position for a small user base |
Why socket capacity is measured on the chassis
The socket test counts every processor socket on the motherboard, empty or filled. A four socket server with two processors installed fails on day one, and leaving sockets empty never makes it eligible. In our experience this is the most expensive misreading of SE2.
It usually starts in the hardware team. Four socket servers get bought for memory channels and future growth, and the database team inherits a machine that can never legally run SE2. Ask for the socket capacity before the purchase order is signed, because the remedy after installation is Enterprise Edition on a server you already own.
Why the core factor table does not apply
SE2 is the only Oracle Database edition that ignores cores completely. The core factor table is an Enterprise Edition instrument, so a 16 core chip and a 64 core chip in the same socket cost the same one license under SE2.
How to Negotiate Your Oracle SaaS Renewal: The Five Moves at the Table
How much does SE2 cost compared with Enterprise Edition?
SE2 lists at $17,500 per occupied socket, so a legal two socket server costs $35,000 whatever the chips contain. Enterprise Edition lists at $47,500 per processor, and processors are counted as cores multiplied by the 0.5 core factor on Intel and AMD hardware.
| Position | License basis | License at list | Support at 22 percent a year |
|---|---|---|---|
| SE2, Processor metric | 2 occupied sockets at $17,500 | $35,000 | $7,700 |
| SE2, Named User Plus floor | 10 users at $350 | $3,500 | $770 |
| Enterprise Edition, 32 cores | 16 processors at $47,500 | $760,000 | $167,200 |
| Enterprise Edition, 128 cores | 64 processors at $47,500 | $3,040,000 | $668,800 |
The two Enterprise Edition rows describe the same class of machine, differing only in chip density, yet the denser one passes $3 million. The SE2 rows stay the same for both, because SE2 never counts cores. Support follows the same pattern, since it is charged as 22 percent of the license fee every year.
Why every hardware refresh widens the gap
Chip vendors keep adding cores per socket. Each refresh raises the Enterprise Edition bill on a two socket box and leaves the SE2 bill at $35,000, so the case for SE2 gets stronger every time you replace hardware.
Few buyers use the edition on purpose. The edition decision was usually made years earlier on a smaller server, and it was never revisited when the new hardware arrived.
Standard Edition 2 licensing brief
How to count sockets, plan thread capacity and negotiate a move off Enterprise Edition.
Get the white paper →Can one SE2 server run several databases?
Yes. The 16 thread ceiling applies to each database, not to the server, so a legal two socket machine with 128 cores can host a dozen SE2 databases on two Processor licenses. The cap governs the speed of each database, and the license count stays at two whatever number of databases the box carries.
For a group of small and medium workloads, that difference is measured in millions of dollars. One planning detail matters if you use pluggable databases. Without the Multitenant option, a container database may hold at most 3 user created PDBs, and those PDBs share the thread ceiling of their container.
A worked consolidation example
Say you run 12 small databases today on three two socket Enterprise Edition servers with 32 cores each. None of them needs more than 16 threads, and none uses an Enterprise Edition option. The table compares that setup with one two socket SE2 server carrying 128 cores.
| Item | Enterprise Edition today | SE2 on one 128 core server |
|---|---|---|
| Servers | 3, with 32 cores each | 1, with 128 cores |
| Licenses needed | 48 processors (16 per server) | 2 Processor licenses |
| License value at list | $2,280,000 | $35,000 |
| Support per year at 22 percent | $501,600 | $7,700 |
| Thread capacity | Not capped | 12 databases at 16 threads is 192, against 256 hardware threads with two threads per core |
If you already own the Enterprise Edition licenses, that license spend is sunk. The new outlay is $35,000 for the SE2 licenses, and the saving you can book each year is the gap between the two support lines. How much of that gap you keep depends on Oracle's support policies.
What Oracle's support policies do to that saving
Oracle's Technical Support Policies put Enterprise Edition and SE2 in the same license set, because the editions share source code. You cannot leave Enterprise Edition licenses unsupported on the shelf while paying support on SE2. The unsupported licenses must be terminated.
Terminating a subset of licenses on one order also triggers repricing. Support on the licenses left on that order is recalculated at Oracle's list support price minus the standard discount, capped at the fees you paid before. Model this order by order before you tell Oracle anything, and look for orders you can end in full.
How has Oracle changed Standard Edition since 2015?
Oracle has narrowed the edition twice in ten years without moving the price. Before 2015, Standard Edition allowed four sockets and Standard Edition One allowed two at a lower price.
- 2015, release 12.1.0.2. Oracle retired both products and moved customers to SE2, which carries the tighter two socket limit. Existing customers could move to SE2 without an additional license fee, but anyone running Standard Edition on four socket hardware had to shrink the machine or step up to Enterprise Edition.
- 2019, release 19c. Real Application Clusters was removed from Standard Edition entirely, which cost every SE2 site running a two node cluster.
- Release Update 19.7. Standard Edition High Availability arrived as partial relief. It uses Oracle Clusterware to restart a single instance database on a failover node, which gives you failover with one node serving users at a time.
Data Guard is also an Enterprise Edition feature, so SE2 standby databases rely on other methods. We cover the options in our note on high availability after SE2 lost RAC.
How to hold an SE2 position given that history
That history is a reason to keep careful records around an SE2 position. The saving is available today, and the terms are Oracle's to revise at the next release.
Take the saving and keep it documented, so you can assess any future change quickly. For every SE2 database, record:
- the server it runs on and that server's socket capacity, with the hardware specification on file
- evidence that the database runs comfortably under the 16 thread ceiling
- what the Enterprise Edition fallback would cost if a future release narrows the edition again
Read the Licensing Information manual for every new release before you schedule the upgrade, since that is where a narrowed edition first shows up.
Where do SE2 audit findings come from?
They come from socket capacity, the user floor and Enterprise Edition software running under an SE2 order. The thread cap is not a source of findings, because the database enforces it and you cannot exceed it by accident.
The socket finding is the costly one. Oracle's proposed remedy for a server with four socket capacity is to relicense it as Enterprise Edition per processor at $47,500 after core factor, plus support arrears.
How to check your own position
- Socket capacity. Read the server's hardware specification, or run dmidecode -t processor on Linux, which lists every socket and marks empty ones as unpopulated. Tools that report only installed processors will miss empty sockets.
- Edition installed. Query v$version on each database. The banner names the edition, and it must match what your order says.
- Feature and pack usage. Check DBA_FEATURE_USAGE_STATISTICS. The Diagnostics and Tuning Packs cannot be licensed on SE2 at all, so CONTROL_MANAGEMENT_PACK_ACCESS should be set to NONE. Our note on management packs in the feature usage view explains what to look for.
- Virtual hosts. On VMware, Oracle's partitioning policy treats the hypervisor as soft partitioning, and Oracle will expect every host the virtual machine could run on to be licensed. For SE2 each of those hosts also needs two socket capacity, so keep SE2 guests on a cluster built only from two socket hosts.
- Users. If you license by Named User Plus, keep a dated list of every authorized person and device per server.
The commercial terms sit on Oracle's SE2 product page and price list. The binding rules sit in the Database Licensing Information manual, which is the document an auditor will quote back to you, so read the two together.
The measurement method is set out in our Standard Edition 2 guide, and the three axis view of every edition is in Oracle Database licensing.
When does Named User Plus make sense for SE2?
Named User Plus makes sense for internal applications with a stable user base you can name. It is the SE2 option we see underused most often, and it can cut the cost of a small database by an order of magnitude.
- The floor is 10 Named User Plus per server at $350 list, so a small internal application is fully licensed for $3,500.
- Authorization is the test. Count every human and every device authorized to use the database, whether or not they log in this quarter.
- Multiplexing does not reduce the count. Users behind an application server, a portal or a reporting tool are counted anyway, whether the pooling happens in hardware or software. See how Oracle counts users behind a front end.
- Internet facing or unknown populations fail the metric. If you cannot name the users, you cannot count them, and Named User Plus is not available.
- Compare the two metrics server by server. The answer can differ machine by machine, so a single decision for all your servers usually leaves money on the table.
Where the crossover sits
On a two socket server the Processor position costs $35,000, which buys 100 Named User Plus at $350. Below 100 users per server, Named User Plus is cheaper. On a one socket server the crossover is 50 users.
Say an internal finance application has 40 staff and 2 batch servers that write to the database. That is 42 Named User Plus, or $14,700 at list, against $35,000 for the two socket Processor position. Remember that non human devices count as users.
How is SE2 licensed in AWS, Azure and Google Cloud?
In Oracle's authorized cloud environments, every 4 vCPUs count as one socket, rounded up. SE2 may only run on instances with up to 8 vCPUs, which makes the largest SE2 cloud instance equal to two sockets, or $35,000 at list.
When licensing by Named User Plus in those clouds, the minimum is 10 Named User Plus per 8 vCPUs. The wider rules for bringing licenses to those clouds are in our guide to the Oracle cloud licensing policy.
What have we seen in SE2 reviews in 2024 and 2025?
Across roughly 20 to 30 Oracle Database environments we reviewed in 2024 to 2025, SE2 was underused where it fitted and misapplied where it did not, and each error carried its own cost.
- Overpaying on Enterprise Edition. Workloads that sat comfortably inside every SE2 rule ran on Enterprise Edition anyway and paid 3 to 6 times more, for capacity no one had asked for.
- Savings from matching the edition. Buyers who chose the edition by the actual rules, rather than by ambition, cut database license and support cost by 25 to 45 percent.
- Compliance gaps. Where SE2 was out of compliance, the cause was almost never threads. It was a server with four socket capacity, or an Enterprise Edition install running under an SE2 order.
- Upgrade surprises. Sites that moved to 19c without reading the release notes lost SE2 RAC during the upgrade window.
Why we push back on standardizing everything on Enterprise Edition
A common recommendation from DBA teams and some advisors is to run one edition everywhere, usually Enterprise Edition, so that no database ever hits a limit. We disagree for workloads that fit the SE2 rules. The overpay described above buys capacity those databases do not use.
The better course is to pick the edition server by server and write down why. Keep Enterprise Edition where a database needs more than 16 threads, uses an Enterprise option, or needs Data Guard. Move the rest to SE2 on two socket hardware.
SE2 licenses the socket and ignores what is inside it, so every hardware refresh makes the edition cheaper relative to Enterprise Edition.
What will Oracle's account team say about moving to SE2?
Expect resistance, because a move to SE2 reduces Oracle's support revenue. These are the lines we hear most, with the replies that hold up.
| What Oracle says | What to say back |
|---|---|
| Your databases use Enterprise Edition features, so SE2 is not an option. | Name the feature for each database. We will check it against DBA_FEATURE_USAGE_STATISTICS and move only the databases that use none. |
| If you terminate Enterprise Edition licenses, your remaining support will be repriced. | We have modeled the repricing order by order. Show us your calculation for each order so we can compare it with ours. |
| SE2 lost RAC, so it is not suitable for production. | Standard Edition High Availability gives failover for single instance databases. Our recovery time target for these applications is met by failover. |
| Your VMware cluster includes four socket hosts, so SE2 cannot run there. | The SE2 guests sit on a separate cluster of two socket hosts. Here is the host list, and here is the vMotion boundary that keeps them on it. |
| Consolidate on Enterprise Edition with Multitenant instead. | Quote that in writing next to the SE2 price for the same databases, including options and support. |
Questions to settle before you sign an SE2 order
- Which servers will run the SE2 databases, and do you hold the hardware specification showing two socket capacity for each one?
- Which of our current support orders would be repriced if we terminate Enterprise Edition licenses, and by how much?
- Will Oracle hold the SE2 Processor and Named User Plus price for additional licenses over the next two to three years?
- If any of these databases will move to AWS, Azure or Google Cloud, which instance sizes keep them within the 8 vCPU limit for SE2?
What to do next
- Before any hardware purchase. Record the socket capacity of every server, counting empty sockets as well as occupied ones, and flag every machine with capacity above two as ineligible for SE2 regardless of what is fitted.
- Twelve months before your support renewal. List every database that runs under 16 threads of user execution and check whether it sits on Enterprise Edition for a reason anyone can name.
- Nine months before. Price the consolidation: how many of those databases could share one legal two socket server on two Processor licenses.
- Six months before. Test the Named User Plus floor per server against the Processor position, because the answer differs machine by machine.
- Three months before. Model support repricing for each order you would reduce, and decide which orders to end in full.
- Before the next database release. Document the position, since the edition has narrowed twice in ten years. Our Oracle practice runs the edition review with you, and the wider library sits in the Oracle knowledge hub.
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 Oracle Standard Edition 2?
SE2 is Oracle's lower priced database edition for servers with at most two sockets. It replaced Standard Edition and Standard Edition One in 2015, is licensed per occupied socket or by Named User Plus, ignores core counts, and excludes Enterprise Edition options, the management packs, Data Guard and, since 19c, RAC.
What does SE2 cost?
List price is $17,500 per occupied socket, and annual support is 22 percent of the net license fee, or $3,850 per socket at list. By Named User Plus the price is $350 per user, with a floor of 10 users on every server. A fully licensed two socket server therefore costs between $3,500 and $35,000 at list, depending on the metric.
Is the socket rule about sockets used or sockets available?
Sockets available. Oracle's wording is maximum capacity, so a server with four sockets and two chips is ineligible from the day it is installed. Get the socket count from the hardware specification before you buy, because a hardware quote usually lists only the processors being shipped.
Does the 16 thread cap limit the server?
No. The cap applies to each database instance, and the rest of the server's threads stay available to other SE2 databases on the same box. The Processor license count depends only on occupied sockets. Size the hardware on the combined peak thread demand of every database it will carry.
Can we accidentally breach the thread cap?
No. SE2 restricts itself to 16 CPU threads at any time, whatever the hardware offers, so the cap cannot create a license debt. A database that needs more CPU shows it as slower response. The answer then is tuning, or moving that one workload to Enterprise Edition, never a compliance payment.
How much cheaper is SE2 than Enterprise Edition?
On a two socket server with 128 cores, the license is $35,000 against $3.04m at list, so SE2 costs just over 1 percent of the Enterprise Edition price, because Enterprise Edition needs 64 processor licenses after core factor. In the environments we reviewed, workloads that fitted the SE2 rules but ran on Enterprise Edition paid 3 to 6 times more.
What happened to RAC on Standard Edition?
Oracle removed Real Application Clusters from SE2 in 19c. Its replacement, Standard Edition High Availability from Release Update 19.7, restarts a single instance database on a second node through Oracle Clusterware. If an application relied on two active nodes, test how it behaves during a failover restart before you upgrade.
When does Named User Plus beat the processor metric?
When a two socket server has fewer than 100 authorized users and devices, or a one socket server fewer than 50, and you can name every one of them. Public websites, customer portals and any population you cannot list do not qualify, whatever the numbers say.
Does putting users behind an application reduce the count?
No. Oracle counts the people and devices in front of any pooling layer, so a portal that connects 300 staff through one database account needs 300 Named User Plus. The same applies to reporting tools, middleware and batch interfaces that feed the database.
What does a socket capacity breach cost to fix?
Oracle's opening position is Enterprise Edition per processor at $47,500 after core factor, plus back support. On a 32 core server that is $760,000 of license before arrears. Replacing the hardware afterwards stops the exposure going forward but does not erase the period already run.