Wednesday, March 21, 2012
Processor Licensing question
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 affinity?
I'm rapidly learning that the second processor in this machine is pretty much completely unused. Is there a way in setup or in a config file or something for SQL Server 2005 to tell it to use the second processor?
Thanks in advance...
-Eric HarmonThis is for SQL 2000, but anyway: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_config_5lfd.asp
Make sure you're not running SQL 2005 Express, it only supports one processor...
Processor affinity.
executing on?I am not 100% sure, but I think profiler will show the proc#.. ( could be
mistaken tho.)
--
Wayne Snyder MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
(Please respond only to the newsgroups.)
I support the Professional Association for SQL Server
(www.sqlpass.org)
<KJGNews@.hotmail.com> wrote in message
news:efaW6PywDHA.2460@.TK2MSFTNGP10.phx.gbl...
> Is there any way of finding out which processors a SPID is
> executing on?
>
'Processor Affinity from server properties
Hi everyone,
Primary platform is 2005 under 64-bit.
I'm trying to figure out what does 'Processor Affinity' and 'I/O Affinity' means when you're viewing server properties. We've got eight processors.
Thanks for your comments,
Processor Affinity is the list of processors that worker threads are allowed to execute on. The number is a bit mask with one bit aligning to each processor on the system. A value of 0 allows use of all processors.
I/O affinity mask is the list of processors that are allowed to process IO operations, and uses the same bitmask scheme.
In most cases there is no need to change either setting. If you do decide to make changes to either setting ensure that the same processor is not specified in both masks.
|||thankssql
'Processor Affinity from server properties
Hi everyone,
Primary platform is 2005 under 64-bit.
I'm trying to figure out what does 'Processor Affinity' and 'I/O Affinity' means when you're viewing server properties. We've got eight processors.
Thanks for your comments,
Processor Affinity is the list of processors that worker threads are allowed to execute on. The number is a bit mask with one bit aligning to each processor on the system. A value of 0 allows use of all processors.
I/O affinity mask is the list of processors that are allowed to process IO operations, and uses the same bitmask scheme.
In most cases there is no need to change either setting. If you do decide to make changes to either setting ensure that the same processor is not specified in both masks.
|||thanks