Standard Edition is dead – long live Standard Edition 2

Update 8th July – the plot thickens

After posting this blog two days ago, it seems Oracle Corp. may be taking a little time out to “clarify” their position. The original MOS note referenced below is no longer available (despite the link still sitting in my favourites in MOS), and furthermore, the helpful and rather detailed blog post by Mike Dietrich (News on Oracle Database STANDARD EDITION has been redacted to a “watch this space” note.

So I guess we’ll have to watch this space…

My original blog posting from 6th July remains below.

Disclaimer – these are my personal musings based on very limited information, which I’m sure will rapidly become out of date as more details emerge over the coming months.

After a year of uncertainty, Oracle has finally announced the future of Standard Edition (SE). Along with its smaller sibling Standard Edition 1 (SE1), it is being retired and replaced by Standard Edition 2 (SE2). Perhaps the most significant point of this change is that SE2 can only be run on one- or two-socket servers, which raises interesting questions for existing SE deployments on four-socket servers.

When was released in July 2014, it was only available for Enterprise Edition (EE). No date was given for SE and SE1, and with patching for scheduled to end in July 2015, there was an uncertain future for SE and SE1. With Extended Support fees waived on 11g for a year, it seemed like sticking with 11g was a better option for SE and SE1 than moving to 12c with no clear future. However, with 11g ending Premier Support in early 2015, things were beginning to look very bleak for Oracle’s most cost-effective database platforms.

After months of silence, a MOS note was quietly published in early July 2015 (2027072.1) with a rather surprise announcement. The key points I took from this brief note are :

  • is the final release for SE and SE1
  • Beginning with, SE and SE1 will be superseded by SE2
  • SE2 can be run on a maximum of 2 sockets, and can optionally support a two-node RAC cluster
  • Customers running SE or SE1 will have to migrate their licenses to SE2 if they wish to upgrade to (i.e. if they wish to remain supported beyond January 2016)
  • SE2 is scheduled for release in Q3 2015
  • Patching for SE and SE1 will be extended until January 2016, beyond the originally published date of July 2015

So what does this mean for SE and SE1 users?

Firstly, there’s a small lifeline, in that will be patched for another six months. However, if like me you’ve stuck with 11g and haven’t yet upgraded to 12c, is it really worth upgrading for a further six months, when 11g remains in (fees-waived) Extended Support for the same period?

The most interesting point is what happens to systems running SE on a 4-socket system, or a 2×2-socket RAC system. When the lights finally go out on SE and SE1 in January 2016, you will have to migrate to different hardware to keep within the 2-socket limit. Alternatively you may be faced with a large bill to upgrade to EE.

There’s been no mention of pricing yet. It’s been suggested that the cost of SE2 could fall somewhere between SE1 and SE. However, with the MOS note saying you have to migrate your licenses in order to upgrade, I wonder how many customers will end up paying Oracle for the privilege of migrating. Cue some lengthy discussions with your favourite account manager.

What will SE2 look like? Will it keep to the same limited set of features as SE/SE1, or will a few EE features or options be allowed to creep in? Parallel execution would be a nice treat. Will SE2 offer any improved performance monitoring capabilities, or will we still be forced to hunt around for the install script for Statspack?

Finally, will Oracle use this as an opportunity to retire the per-socket metric for licensing of SE/SE1, instead moving to per-core licensing, as is done with EE? With the advance of multi-core chips, it seems inevitable at some point. Again, this could adversely impact customers who have invested in high-end multi-core chips.

I’m no lawyer, but having recently been debating perpetual vs term licenses, it makes me wonder what “Perpetual” really means, when support for said license is no longer available. I’m sure it’s in the small print somewhere.


4 thoughts on “Standard Edition is dead – long live Standard Edition 2

  1. John Hallas

    Very interesting find Dan. I like your analysis as well.
    I would think an acceptable solution would be for Oracle to say that all new servers that do not meet the SE2 core requirements should be licensed on SE2 but existing ones should be able to migrate FOC – but there again that is me being reasonable – I don’t have income targets to meet


  2. Simon Haslam

    Interesting stuff! It’s certainly true that the advancement of processors over the last decade has meant that you can run rather a lot of very fast cores on a 2-socket SE1 licence… you can probably even buy a server that is more expensive than the database licence for once!

    I remember when SE1 first came out – IIRC it was mostly to have a low priced entry point to compete with MS SQLserver. The situation is a bit different now so I wouldn’t blame Oracle for reviewing the editions, though let’s hope they are fair to customers who have already invested in SE/SE1.

    Regarding whether SE might become licensed by core rather than socket, that is a general Oracle licensing rule (i.e. anything with “Standard Edition” in the title). Therefore to change that they would need to either make a special case for the database, or else update the general rule (since similar arguments apply) – this would have an impact on other products (such as WebLogic Server Standard Edition).



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s