Story Source and Credit: Keith Alsheimer, Chief Marketing Officer at EnterpriseDB
November 24, 2015
As of December 1, 2015, Oracle® is no longer offering two of its most popular database license options, SE and SE1; replacing them instead with a new SE2 version which effectively increases license limitations to force more customers onto their Enterprise Edition—at an enormous cost increase. This dramatic change is forcing many existing Oracle SE and SE1 users into the unwelcome dilemma of having to choose the least bad of the costly and disruptive options available to them.
This is just one more example of the tyrannical practices that have given Oracle such an infamously gluttonous reputation for so many years. But just as fed-up American colonists once threw a shipload of tea into the Boston Harbor to protest excessive taxation, sometimes tyranny can be a forge for unexpected liberation.
For those who may not yet know all the details, Oracle has eliminated SE and SE1 database license options beginning with its 126.96.36.199 release and replaced them with a new version called Oracle SE2. SE2 will cost 20% more than SE1, and while the same price as SE, will provide 50% less capacity by reducing the maximum allowable footprint from 4 sockets down to just 2 with a maximum of 16 CPU threads per instance. Minimum named user plus licenses are also increased from 5 to 10 and Real Application Cluster (RAC) maximum deployments are now limited to 2 clusters of one socket each with a maximum of 8 CPU threads per instance at any time.
After a long string of disappointing earnings results, Oracle seems intent on forcing more Oracle Enterprise Edition license sales at far greater cost ($47,500 per core plus add-ons vs. $17,500 per socket) along with higher ongoing maintenance fees (22% of license cost).
While this will certainly affect purchasing decision options for prospective new customers, it has a far bigger impact on existing users, particularly those with an Oracle SE license. Here’s what it means for an average Oracle customer running SE on a 4-socket server using 8-core processors per socket. Since a Oracle SE2 maximum deployment is a 2-socket server, the user must pay an astonishing 4,000% cost increase to move to Enterprise Edition and license 32 cores, or “upgrade” to SE2 and buy two new database servers each with a maximum capacity of 2 sockets then split the deployment across the two servers.
However, if Oracle RAC were part of the deployment, then the SE2 limitation would only allow 1 socket per node with a maximum limit of 2 nodes and 8 CPU threads per instance. This would therefore most likely require either reengineering the application or accepting reduced performance capacity of the cluster.
Full Story Here……..