Oracle per core vs per user: which one fits and why they push the expensive one
The sales rep almost always steers you to the model that pays them best, not you.
Oracle can be licensed two ways: per processor or per named user (Named User Plus). For many companies with few users and large servers, the per-user model is dramatically cheaper. The catch is that it is almost never the first thing they propose.
01 Per processor: you pay for hardware, not for people
This model charges by the server's cores, whether 5 or 5,000 people use it. It fits when you have many users or internet-facing access that is impossible to count.
02 Per named user: you pay by head count
Named User Plus charges for each person or device that accesses the database. If you have a small, well-defined set of internal users, the savings are enormous.
03 Watch the per-core user minimum
Enterprise Edition requires a minimum of 25 named users per processor. That floor is what makes the per-user model stop paying off once the server gets large.
25-user minimum per processor
04 Why they push the expensive one
The per-processor model usually produces a bigger bill and scales up more easily. It is convenient for whoever is selling. Your job is to ask for both options and compare with real numbers.
// An illustrative case
Imagine an internal database used by 40 employees, running on an 8-core server (4 Oracle processors after the factor). Per processor: 4 x USD $47,500 = USD $190,000. Per named user, at the 25-per-processor minimum, that is 100 users: 100 x USD $950 = USD $95,000. Half the cost, just by choosing the right model.
Illustrative example with typical market figures, not a specific client.
// next step
Choosing the right model comes down to counting your users and cores correctly. A quick scan tells you which one fits without guessing. At dba.mx we work at a fixed price, with no surprises at the end.