RE: oracle EE pricing
- From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
- To: "pythianbrinsmead@xxxxxxxxx" <pythianbrinsmead@xxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 19 Jan 2010 10:23:02 -0700
Ok, I think I figured out how I was misinterpreting it. I was misreading it as
"a _core_ is counted equivalent to a socket", meaning that you could only run
on a max of 2 cores, regardless of whether it was one dual-core CPU, or two
single-core CPUs. After rereading it a few times and some anonymous off-list
help, I think what they actually mean by "a _processor_ is counted equivalent
to a socket", is that each processor/socket is counted only once for licensing
regardless of the number of cores it has. If you have two sockets you pay the
same regardless of how many cores they have, so the price is the same for two
dual-cores as it is for two quad-cores or two six-ways; you're only charged for
TWO processor licenses even though you may be running 4, 8 or 12 cores. I
think I went through this same misunderstanding a few years ago but already
forgot about it. Can anyone confirm if I have it right now?
Thanks,
Brandon
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Allen, Brandon
Mark, are you sure it's permitted to license SE-1 on a 12-core server? I
thought SE1 could only be licensed on a max of 2 cores according to this
________________________________
Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do not
consent to Internet email for messages of this kind. Opinions, conclusions and
other information in this message that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it.
Other related posts:
- » oracle EE pricing- Veres Lajos
- » RE: oracle EE pricing- Johnson, William L (TEIS)
- » Re: oracle EE pricing- Mark Brinsmead
- » Re: oracle EE pricing- Fergal Taheny
- » RE: oracle EE pricing- William Muriithi
- » Re: oracle EE pricing- Nigel Thomas
- » RE: oracle EE pricing- Goulet, Richard
- » Re: oracle EE pricing- Nigel Thomas
- » RE: oracle EE pricing- Goulet, Richard
- » Re: oracle EE pricing- Thomas Roach
- » RE: oracle EE pricing- Michael McMullen
- » RE: oracle EE pricing- Goulet, Richard
- » Re: oracle EE pricing- vit\.spinka
- » Re: oracle EE pricing- Barbara Baker
- » Re: oracle EE pricing- Kellyn Pedersen
- » RE: oracle EE pricing- Matthew Zito
- » RE: oracle EE pricing- Goulet, Richard
- » Re: oracle EE pricing- Mark Brinsmead
- » Re: oracle EE pricing- Mark Brinsmead
- » RE: oracle EE pricing- Matthew Zito
- » Re: oracle EE pricing- Gints Plivna
- » RE: oracle EE pricing- Goulet, Richard
- » RE: oracle EE pricing- Joel.Patterson
- » RE: oracle EE pricing- Goulet, Richard
- » RE: oracle EE pricing- Goulet, Richard
- » RE: oracle EE pricing- Allen, Brandon
- » RE: oracle EE pricing- Michael McMullen
- » Re: oracle EE pricing- Bradd Piontek
- » RE: oracle EE pricing- Michael McMullen
- » RE: oracle EE pricing - Allen, Brandon
- » Re: oracle EE pricing- Niall Litchfield
- » Re: oracle EE pricing- Gints Plivna
- » Re: oracle EE pricing- John Thompson
- » Re: oracle EE pricing- Mark Brinsmead
- » Re: oracle EE pricing- Mark Brinsmead
- » Re: oracle EE pricing- Kellyn Pedersen