Showing posts with label partitioning. Show all posts
Showing posts with label partitioning. Show all posts

Wednesday, March 21, 2012

Processor License

I read the FAQ at
http://www.microsoft.com/sql/howtobuy/partitioning.asp, but it is still
not clear to me how to buy processor licenses basing on the number of
processors
The FAQ states
"If any processor in the server is made inaccessible to all of the
operating system copies set up to run SQL Server, then that processor
does not require a Processor license for SQL Server. In other words, a
SQL Server Processor license is required for each processor that is
accessible to any operating system copy on which SQL Server is set up
to run. "
Does this mean that the only way to avoid buying multiple processor
licenses is disabling the processor from the server's BIOS?
I guess that the "processor control" tab in the SQL server properties
has nothing to do with this, even if I'd find it very wise if MS
provided us with such a tool...
I also guess that they mean physical processor AND NOT virtual
processor deriving from Hyperthreading...
Thanks
Dave
> Does this mean that the only way to avoid buying multiple processor
> licenses is disabling the processor from the server's BIOS?
That is how I understand it.

> I also guess that they mean physical processor AND NOT virtual
> processor deriving from Hyperthreading...
Yep
Keith
<dbwmn2001@.yahoo.com> wrote in message
news:1106241266.515795.105740@.c13g2000cwb.googlegr oups.com...
> I read the FAQ at
> http://www.microsoft.com/sql/howtobuy/partitioning.asp, but it is still
> not clear to me how to buy processor licenses basing on the number of
> processors
> The FAQ states
> "If any processor in the server is made inaccessible to all of the
> operating system copies set up to run SQL Server, then that processor
> does not require a Processor license for SQL Server. In other words, a
> SQL Server Processor license is required for each processor that is
> accessible to any operating system copy on which SQL Server is set up
> to run. "
> Does this mean that the only way to avoid buying multiple processor
> licenses is disabling the processor from the server's BIOS?
> I guess that the "processor control" tab in the SQL server properties
> has nothing to do with this, even if I'd find it very wise if MS
> provided us with such a tool...
> I also guess that they mean physical processor AND NOT virtual
> processor deriving from Hyperthreading...
> Thanks
> Dave
>
|||Hi,
Of course per processor licence is for physical processor and not for
Hyperthreading.
As regards disabling is as far as I know exactly as you wrote. You have to
disable processor in BIOS otherwise you should buy a licence.
Danijel
<dbwmn2001@.yahoo.com> wrote in message
news:1106241266.515795.105740@.c13g2000cwb.googlegr oups.com...
>I read the FAQ at
> http://www.microsoft.com/sql/howtobuy/partitioning.asp, but it is still
> not clear to me how to buy processor licenses basing on the number of
> processors
> The FAQ states
> "If any processor in the server is made inaccessible to all of the
> operating system copies set up to run SQL Server, then that processor
> does not require a Processor license for SQL Server. In other words, a
> SQL Server Processor license is required for each processor that is
> accessible to any operating system copy on which SQL Server is set up
> to run. "
> Does this mean that the only way to avoid buying multiple processor
> licenses is disabling the processor from the server's BIOS?
> I guess that the "processor control" tab in the SQL server properties
> has nothing to do with this, even if I'd find it very wise if MS
> provided us with such a tool...
> I also guess that they mean physical processor AND NOT virtual
> processor deriving from Hyperthreading...
> Thanks
> Dave
>
|||Disabling in BIOS or physically removing a processor is the only way to keep
from counting a processor towards licensing requirements. If the OS sees
it, you must license it.
"Processors" means physical processors, not logical processors. Turning
HyperThreading on or off has no effect on licensing requirements.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
<dbwmn2001@.yahoo.com> wrote in message
news:1106241266.515795.105740@.c13g2000cwb.googlegr oups.com...
> I read the FAQ at
> http://www.microsoft.com/sql/howtobuy/partitioning.asp, but it is still
> not clear to me how to buy processor licenses basing on the number of
> processors
> The FAQ states
> "If any processor in the server is made inaccessible to all of the
> operating system copies set up to run SQL Server, then that processor
> does not require a Processor license for SQL Server. In other words, a
> SQL Server Processor license is required for each processor that is
> accessible to any operating system copy on which SQL Server is set up
> to run. "
> Does this mean that the only way to avoid buying multiple processor
> licenses is disabling the processor from the server's BIOS?
> I guess that the "processor control" tab in the SQL server properties
> has nothing to do with this, even if I'd find it very wise if MS
> provided us with such a tool...
> I also guess that they mean physical processor AND NOT virtual
> processor deriving from Hyperthreading...
> Thanks
> Dave
>

Processor License

I read the FAQ at
http://www.microsoft.com/sql/howtobuy/partitioning.asp, but it is still
not clear to me how to buy processor licenses basing on the number of
processors
The FAQ states
"If any processor in the server is made inaccessible to all of the
operating system copies set up to run SQL Server, then that processor
does not require a Processor license for SQL Server. In other words, a
SQL Server Processor license is required for each processor that is
accessible to any operating system copy on which SQL Server is set up
to run. "
Does this mean that the only way to avoid buying multiple processor
licenses is disabling the processor from the server's BIOS?
I guess that the "processor control" tab in the SQL server properties
has nothing to do with this, even if I'd find it very wise if MS
provided us with such a tool...
I also guess that they mean physical processor AND NOT virtual
processor deriving from Hyperthreading...
Thanks
DaveHi,
Of course per processor licence is for physical processor and not for
Hyperthreading.
As regards disabling is as far as I know exactly as you wrote. You have to
disable processor in BIOS otherwise you should buy a licence.
Danijel
<dbwmn2001@.yahoo.com> wrote in message
news:1106241266.515795.105740@.c13g2000cwb.googlegroups.com...
>I read the FAQ at
> http://www.microsoft.com/sql/howtobuy/partitioning.asp, but it is still
> not clear to me how to buy processor licenses basing on the number of
> processors
> The FAQ states
> "If any processor in the server is made inaccessible to all of the
> operating system copies set up to run SQL Server, then that processor
> does not require a Processor license for SQL Server. In other words, a
> SQL Server Processor license is required for each processor that is
> accessible to any operating system copy on which SQL Server is set up
> to run. "
> Does this mean that the only way to avoid buying multiple processor
> licenses is disabling the processor from the server's BIOS?
> I guess that the "processor control" tab in the SQL server properties
> has nothing to do with this, even if I'd find it very wise if MS
> provided us with such a tool...
> I also guess that they mean physical processor AND NOT virtual
> processor deriving from Hyperthreading...
> Thanks
> Dave
>|||> Does this mean that the only way to avoid buying multiple processor
> licenses is disabling the processor from the server's BIOS?
That is how I understand it.
> I also guess that they mean physical processor AND NOT virtual
> processor deriving from Hyperthreading...
Yep
--
Keith
<dbwmn2001@.yahoo.com> wrote in message
news:1106241266.515795.105740@.c13g2000cwb.googlegroups.com...
> I read the FAQ at
> http://www.microsoft.com/sql/howtobuy/partitioning.asp, but it is still
> not clear to me how to buy processor licenses basing on the number of
> processors
> The FAQ states
> "If any processor in the server is made inaccessible to all of the
> operating system copies set up to run SQL Server, then that processor
> does not require a Processor license for SQL Server. In other words, a
> SQL Server Processor license is required for each processor that is
> accessible to any operating system copy on which SQL Server is set up
> to run. "
> Does this mean that the only way to avoid buying multiple processor
> licenses is disabling the processor from the server's BIOS?
> I guess that the "processor control" tab in the SQL server properties
> has nothing to do with this, even if I'd find it very wise if MS
> provided us with such a tool...
> I also guess that they mean physical processor AND NOT virtual
> processor deriving from Hyperthreading...
> Thanks
> Dave
>|||Disabling in BIOS or physically removing a processor is the only way to keep
from counting a processor towards licensing requirements. If the OS sees
it, you must license it.
"Processors" means physical processors, not logical processors. Turning
HyperThreading on or off has no effect on licensing requirements.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
<dbwmn2001@.yahoo.com> wrote in message
news:1106241266.515795.105740@.c13g2000cwb.googlegroups.com...
> I read the FAQ at
> http://www.microsoft.com/sql/howtobuy/partitioning.asp, but it is still
> not clear to me how to buy processor licenses basing on the number of
> processors
> The FAQ states
> "If any processor in the server is made inaccessible to all of the
> operating system copies set up to run SQL Server, then that processor
> does not require a Processor license for SQL Server. In other words, a
> SQL Server Processor license is required for each processor that is
> accessible to any operating system copy on which SQL Server is set up
> to run. "
> Does this mean that the only way to avoid buying multiple processor
> licenses is disabling the processor from the server's BIOS?
> I guess that the "processor control" tab in the SQL server properties
> has nothing to do with this, even if I'd find it very wise if MS
> provided us with such a tool...
> I also guess that they mean physical processor AND NOT virtual
> processor deriving from Hyperthreading...
> Thanks
> Dave
>

Processor License

I read the FAQ at
http://www.microsoft.com/sql/howtobuy/partitioning.asp, but it is still
not clear to me how to buy processor licenses basing on the number of
processors
The FAQ states
"If any processor in the server is made inaccessible to all of the
operating system copies set up to run SQL Server, then that processor
does not require a Processor license for SQL Server. In other words, a
SQL Server Processor license is required for each processor that is
accessible to any operating system copy on which SQL Server is set up
to run. "
Does this mean that the only way to avoid buying multiple processor
licenses is disabling the processor from the server's BIOS?
I guess that the "processor control" tab in the SQL server properties
has nothing to do with this, even if I'd find it very wise if MS
provided us with such a tool...
I also guess that they mean physical processor AND NOT virtual
processor deriving from Hyperthreading...
Thanks
Dave> Does this mean that the only way to avoid buying multiple processor
> licenses is disabling the processor from the server's BIOS?
That is how I understand it.

> I also guess that they mean physical processor AND NOT virtual
> processor deriving from Hyperthreading...
Yep
Keith
<dbwmn2001@.yahoo.com> wrote in message
news:1106241266.515795.105740@.c13g2000cwb.googlegroups.com...
> I read the FAQ at
> http://www.microsoft.com/sql/howtobuy/partitioning.asp, but it is still
> not clear to me how to buy processor licenses basing on the number of
> processors
> The FAQ states
> "If any processor in the server is made inaccessible to all of the
> operating system copies set up to run SQL Server, then that processor
> does not require a Processor license for SQL Server. In other words, a
> SQL Server Processor license is required for each processor that is
> accessible to any operating system copy on which SQL Server is set up
> to run. "
> Does this mean that the only way to avoid buying multiple processor
> licenses is disabling the processor from the server's BIOS?
> I guess that the "processor control" tab in the SQL server properties
> has nothing to do with this, even if I'd find it very wise if MS
> provided us with such a tool...
> I also guess that they mean physical processor AND NOT virtual
> processor deriving from Hyperthreading...
> Thanks
> Dave
>|||Hi,
Of course per processor licence is for physical processor and not for
Hyperthreading.
As regards disabling is as far as I know exactly as you wrote. You have to
disable processor in BIOS otherwise you should buy a licence.
Danijel
<dbwmn2001@.yahoo.com> wrote in message
news:1106241266.515795.105740@.c13g2000cwb.googlegroups.com...
>I read the FAQ at
> http://www.microsoft.com/sql/howtobuy/partitioning.asp, but it is still
> not clear to me how to buy processor licenses basing on the number of
> processors
> The FAQ states
> "If any processor in the server is made inaccessible to all of the
> operating system copies set up to run SQL Server, then that processor
> does not require a Processor license for SQL Server. In other words, a
> SQL Server Processor license is required for each processor that is
> accessible to any operating system copy on which SQL Server is set up
> to run. "
> Does this mean that the only way to avoid buying multiple processor
> licenses is disabling the processor from the server's BIOS?
> I guess that the "processor control" tab in the SQL server properties
> has nothing to do with this, even if I'd find it very wise if MS
> provided us with such a tool...
> I also guess that they mean physical processor AND NOT virtual
> processor deriving from Hyperthreading...
> Thanks
> Dave
>|||Disabling in BIOS or physically removing a processor is the only way to keep
from counting a processor towards licensing requirements. If the OS sees
it, you must license it.
"Processors" means physical processors, not logical processors. Turning
HyperThreading on or off has no effect on licensing requirements.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
<dbwmn2001@.yahoo.com> wrote in message
news:1106241266.515795.105740@.c13g2000cwb.googlegroups.com...
> I read the FAQ at
> http://www.microsoft.com/sql/howtobuy/partitioning.asp, but it is still
> not clear to me how to buy processor licenses basing on the number of
> processors
> The FAQ states
> "If any processor in the server is made inaccessible to all of the
> operating system copies set up to run SQL Server, then that processor
> does not require a Processor license for SQL Server. In other words, a
> SQL Server Processor license is required for each processor that is
> accessible to any operating system copy on which SQL Server is set up
> to run. "
> Does this mean that the only way to avoid buying multiple processor
> licenses is disabling the processor from the server's BIOS?
> I guess that the "processor control" tab in the SQL server properties
> has nothing to do with this, even if I'd find it very wise if MS
> provided us with such a tool...
> I also guess that they mean physical processor AND NOT virtual
> processor deriving from Hyperthreading...
> Thanks
> Dave
>sql