Processor Licensing question

If I remember correctly, SQL will automatically limit itself when using
the per processor license. If not, you can set the CPU affinity to 1
to make sure it only uses 1.
George Hester wrote:
> I have a dual processor system. One processor is used for boot operations
> and the other is used for Applications. If I were to install SQL Single
> Processior License on this machine would that be within the Licensing
> restrictions as there is the one processor for Applications or would I nee
d
> another license? Thanks.
> --
> George Hester
> _________________________________"PSPDBA" <DissendiumDBA@.gmail.com> wrote in message
news:1150209890.143128.128400@.f14g2000cwb.googlegroups.com...
> If I remember correctly, SQL will automatically limit itself when using
> the per processor license. If not, you can set the CPU affinity to 1
> to make sure it only uses 1.
>
With Per-Proc licensing you must license SQL Server on all processers
visible to the OS instance where SQL is running.
If you want to run a single proc of SQL on a multi-proc box that is used for
multiple different workloads, you can use Virtual Server 2003 R2, install a
new OS that can only see one processor, and install a single-proc license of
SQL Server on that OS instance.
From:
Virtualization and Multiple Instances
http://www.microsoft.com/sql/howtob...einstances.mspx
Each virtual operating environment running SQL Sever 2005 must have a
processor license for each processor that the virtual machine accesses. If a
copy of SQL Server is running on a physical operating environment, then
processor licenses are required for all of the processors on that physical
server.
David|||I have a dual processor system. One processor is used for boot operations
and the other is used for Applications. If I were to install SQL Single
Processior License on this machine would that be within the Licensing
restrictions as there is the one processor for Applications or would I need
another license? Thanks.
George Hester
_________________________________|||If I remember correctly, SQL will automatically limit itself when using
the per processor license. If not, you can set the CPU affinity to 1
to make sure it only uses 1.
George Hester wrote:
> I have a dual processor system. One processor is used for boot operations
> and the other is used for Applications. If I were to install SQL Single
> Processior License on this machine would that be within the Licensing
> restrictions as there is the one processor for Applications or would I nee
d
> another license? Thanks.
> --
> George Hester
> _________________________________|||"PSPDBA" <DissendiumDBA@.gmail.com> wrote in message
news:1150209890.143128.128400@.f14g2000cwb.googlegroups.com...
> If I remember correctly, SQL will automatically limit itself when using
> the per processor license. If not, you can set the CPU affinity to 1
> to make sure it only uses 1.
>
With Per-Proc licensing you must license SQL Server on all processers
visible to the OS instance where SQL is running.
If you want to run a single proc of SQL on a multi-proc box that is used for
multiple different workloads, you can use Virtual Server 2003 R2, install a
new OS that can only see one processor, and install a single-proc license of
SQL Server on that OS instance.
From:
Virtualization and Multiple Instances
http://www.microsoft.com/sql/howtob...einstances.mspx
Each virtual operating environment running SQL Sever 2005 must have a
processor license for each processor that the virtual machine accesses. If a
copy of SQL Server is running on a physical operating environment, then
processor licenses are required for all of the processors on that physical
server.
David

Processor Licensing question

I have a dual processor system. One processor is used for boot operations
and the other is used for Applications. If I were to install SQL Single
Processior License on this machine would that be within the Licensing
restrictions as there is the one processor for Applications or would I need
another license? Thanks.
--
George Hester
_________________________________If I remember correctly, SQL will automatically limit itself when using
the per processor license. If not, you can set the CPU affinity to 1
to make sure it only uses 1.
George Hester wrote:
> I have a dual processor system. One processor is used for boot operations
> and the other is used for Applications. If I were to install SQL Single
> Processior License on this machine would that be within the Licensing
> restrictions as there is the one processor for Applications or would I need
> another license? Thanks.
> --
> George Hester
> _________________________________|||"PSPDBA" <DissendiumDBA@.gmail.com> wrote in message
news:1150209890.143128.128400@.f14g2000cwb.googlegroups.com...
> If I remember correctly, SQL will automatically limit itself when using
> the per processor license. If not, you can set the CPU affinity to 1
> to make sure it only uses 1.
>
With Per-Proc licensing you must license SQL Server on all processers
visible to the OS instance where SQL is running.
If you want to run a single proc of SQL on a multi-proc box that is used for
multiple different workloads, you can use Virtual Server 2003 R2, install a
new OS that can only see one processor, and install a single-proc license of
SQL Server on that OS instance.
From:
Virtualization and Multiple Instances
http://www.microsoft.com/sql/howtobuy/multipleinstances.mspx
Each virtual operating environment running SQL Sever 2005 must have a
processor license for each processor that the virtual machine accesses. If a
copy of SQL Server is running on a physical operating environment, then
processor licenses are required for all of the processors on that physical
server.
David

Processor licensing

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)

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

|||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|||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

Processor based license will improve performance?

If we use processor based license for SQL Server will that improve
performance compare to CAL based licensing?
Thanks.
RamRam wrote:
> If we use processor based license for SQL Server will that improve
> performance compare to CAL based licensing?
> Thanks.
> Ram
>
no!|||No. It's just a different licence agreement. The software is the same in each
case.
--
David Portas
SQL Server MVP
--|||Performance and License are two different and unrelated things. However, as
a side effect, if by acquiring more licenses (Seat based or Processor based)
you are adding
more users, then, ofcourse, the new users will impact performance.
Gopi
"Ram" <Ramakrishna.pothuganti@.vizual.co.in> wrote in message
news:ejOjuswSFHA.2304@.tk2msftngp13.phx.gbl...
> If we use processor based license for SQL Server will that improve
> performance compare to CAL based licensing?
> Thanks.
> Ram
>sql