or virtual processor like explained in
http://www.microsoft.com/sql/howtobuy/default.mspx
->But what about dual core processor?
->And what about clustering? (if a user install 2 server in cluster mode)
tnxOn Thu, 12 Oct 2006 14:14:40 GMT, Enorme Vigenti wrote:
Quote:
Originally Posted by
>In the processor licensing mode a license is required for each physical
>or virtual processor like explained in
>http://www.microsoft.com/sql/howtobuy/default.mspx
>
>->But what about dual core processor?
Hi Enorme,
You pay per soocket. So a dual-core can run on a single-core license.
And if you have a quad-code CPU with hyperthreading (do such beasts even
exist?), you'd have eight logical processors and still have to pay for
only a single processor license.
Quote:
Originally Posted by
>->And what about clustering? (if a user install 2 server in cluster mode)
If only one server is active and the other is a passice server, used
only to take over from the active server in case of an emergency, you
only need a license for the active server. The passive server can't have
more processors than the active server, though.
If you have two active servers (e.g. using one to offload some of the
reporting tasks), you'll have to license both servers.
Licensing FAQ: http://www.microsoft.com/sql/howtobuy/faq.mspx
--
Hugo Kornelis, SQL Server MVP|||Licensing is per processor, not per core. So if you have one dual core
processor it still counts as one.
In clustering, I believe that you dont have to pay for the 'standby' server
if you do not use it for anything else (if its just standby you only need
one license for two servers in cluster).
MC
"Enorme Vigenti" <Lsimon5@.libero.itwrote in message
news:k5sXg.536$uv5.900@.twister1.libero.it...
Quote:
Originally Posted by
In the processor licensing mode a license is required for each physical
or virtual processor like explained in
http://www.microsoft.com/sql/howtobuy/default.mspx
>
->But what about dual core processor?
->And what about clustering? (if a user install 2 server in cluster mode)
>
tnx
(snip)
Hi MC,
May I suggest that you fix your system clock? The NNTP headers show that
your message was sent on Friday, 15:41 UTC/GMT, but the date on your
message shows as Thursday 19:00 UTC/GMT. That's almost 24 hours
difference.
Quote:
Originally Posted by
Quote:
Originally Posted by
>>Date: Thu, 12 Oct 2006 21:00:33 +0200
(...)
Quote:
Originally Posted by
Quote:
Originally Posted by
>>NNTP-Posting-Date: Fri, 13 Oct 2006 15:41:11 +0000 (UTC)
--
Hugo Kornelis, SQL Server MVP|||I'll pass it on to the admin on the machine I used. Thanks Hugo
MC
"Hugo Kornelis" <hugo@.perFact.REMOVETHIS.info.INVALIDwrote in message
news:5900j21t2g3f5gqrgspj346qsmio9ikth5@.4ax.com...
Quote:
Originally Posted by
On Thu, 12 Oct 2006 21:00:33 +0200, MC wrote:
>
(snip)
>
Hi MC,
>
May I suggest that you fix your system clock? The NNTP headers show that
your message was sent on Friday, 15:41 UTC/GMT, but the date on your
message shows as Thursday 19:00 UTC/GMT. That's almost 24 hours
difference.
>
Quote:
Originally Posted by
Quote:
Originally Posted by
>Date: Thu, 12 Oct 2006 21:00:33 +0200
(...)
Quote:
Originally Posted by
Quote:
Originally Posted by
>NNTP-Posting-Date: Fri, 13 Oct 2006 15:41:11 +0000 (UTC)
>
>
--
Hugo Kornelis, SQL Server MVP
