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

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

Hello everyone,
What is the procedure of changing a SQL 2000 server to processor mode
from per seat?
Thank you
Alex Anderson
The following is unsupported but you may want to check the
link:
Q:How to change the license mode after SQL2000 setup?
http://www.tkdinesh.com/faq/ans/license.html
-Sue
On Mon, 23 Aug 2004 15:18:14 -0700, "Alex Anderson"
<AAnderson@.Murrieta.org> wrote:

>Hello everyone,
> What is the procedure of changing a SQL 2000 server to processor mode
>from per seat?
>Thank you
>Alex Anderson
>
|||Sue,
Interesting link, however Mode is already set to 0 and I'm running
Windows 2003 Server. Although, contained within the same registry key is a
FlipAllow and I'm not sure what this is used for. Perhaps to allow the
switch between Per device and Processor? I have the licenses for two
processes (just purchased them from Microsoft) and now from what I'm told I
might just have to pay for support to re-license SQL. Go figure...
Thank you
Alex Anderson
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:fe6li09llida0kiqg7tksh26hta255i5de@.4ax.com...
> The following is unsupported but you may want to check the
> link:
> Q:How to change the license mode after SQL2000 setup?
> http://www.tkdinesh.com/faq/ans/license.html
> -Sue
> On Mon, 23 Aug 2004 15:18:14 -0700, "Alex Anderson"
> <AAnderson@.Murrieta.org> wrote:
>
sql

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

Hello everyone,
What is the procedure of changing a SQL 2000 server to processor mode
from per seat?
Thank you
Alex AndersonNo, switching between the licensing models is not
permitted.
>--Original Message--
>Hello everyone,
> What is the procedure of changing a SQL 2000 server
to processor mode
>from per seat?
>Thank you
>Alex Anderson
>
>.
>|||The following is unsupported but you may want to check the
link:
Q:How to change the license mode after SQL2000 setup?
http://www.tkdinesh.com/faq/ans/license.html
-Sue
On Mon, 23 Aug 2004 15:18:14 -0700, "Alex Anderson"
<AAnderson@.Murrieta.org> wrote:
>Hello everyone,
> What is the procedure of changing a SQL 2000 server to processor mode
>from per seat?
>Thank you
>Alex Anderson
>|||Sue,
Interesting link, however Mode is already set to 0 and I'm running
Windows 2003 Server. Although, contained within the same registry key is a
FlipAllow and I'm not sure what this is used for. Perhaps to allow the
switch between Per device and Processor? I have the licenses for two
processes (just purchased them from Microsoft) and now from what I'm told I
might just have to pay for support to re-license SQL. Go figure...
Thank you
Alex Anderson
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:fe6li09llida0kiqg7tksh26hta255i5de@.4ax.com...
> The following is unsupported but you may want to check the
> link:
> Q:How to change the license mode after SQL2000 setup?
> http://www.tkdinesh.com/faq/ans/license.html
> -Sue
> On Mon, 23 Aug 2004 15:18:14 -0700, "Alex Anderson"
> <AAnderson@.Murrieta.org> wrote:
> >Hello everyone,
> >
> > What is the procedure of changing a SQL 2000 server to processor mode
> >from per seat?
> >
> >Thank you
> >Alex Anderson
> >
>

processor license

hello
i've got an sql 2005 standard server with a processor license. where can i
set, change or configure this license typ in sql 2005?
thanks
michael> i've got an sql 2005 standard server with a processor license. where can i
> set, change or configure this license typ in sql 2005?
You don't need to configure licensing. The license is a legal agreement
that you are obligated to follow as described in the EULA.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Michael Gloor" <michael.gloor@.bluecare.ch> wrote in message
news:%23kt6W3FWIHA.3940@.TK2MSFTNGP05.phx.gbl...
> hello
> i've got an sql 2005 standard server with a processor license. where can i
> set, change or configure this license typ in sql 2005?
> thanks
> michael
>
>

Processor License

I am going to have to install a web based application on a SQL server that
has 4 processors. The web application will integrate with SQL. I do not
have any control over the users that access this system. I am assuming I
will need to but a 4 processor license for SQL. Is there anyway I can run
SQL on just the 1 processor and buy a single processor license?Here is an article on Microsoft's site. It suggests that you would need to
make the processor unavailable to the OS as well.
http://www.microsoft.com/sql/howtobuy/processor.asp
As always. Contact your reseller for an official answer.
--
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Sarah Kingswell" <sarah.kingswell@.ntlworld.com> wrote in message
news:%23c5oilvlDHA.2592@.TK2MSFTNGP10.phx.gbl...
> I am going to have to install a web based application on a SQL server that
> has 4 processors. The web application will integrate with SQL. I do not
> have any control over the users that access this system. I am assuming I
> will need to but a 4 processor license for SQL. Is there anyway I can run
> SQL on just the 1 processor and buy a single processor license?
>|||In addition to Allan's answer, the general rule by MS has been that IF the
procs are on the motherboard (whether or not you have them disabled for SQL
Server use), you must buy licenses for that proc - or take the proc off of
the motherboard...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Sarah Kingswell" <sarah.kingswell@.ntlworld.com> wrote in message
news:#c5oilvlDHA.2592@.TK2MSFTNGP10.phx.gbl...
> I am going to have to install a web based application on a SQL server that
> has 4 processors. The web application will integrate with SQL. I do not
> have any control over the users that access this system. I am assuming I
> will need to but a 4 processor license for SQL. Is there anyway I can run
> SQL on just the 1 processor and buy a single processor license?
>|||Hi Wayne!
> In addition to Allan's answer, the general rule by MS has been that IF the
> procs are on the motherboard (whether or not you have them disabled for SQL
> Server use), you must buy licenses for that proc - or take the proc off of
> the motherboard...
In the word doc released in May, MS softened down this a bit. Here's a quote:
You must acquire licenses for only those processors that are accessible to any operating system copy
upon which the Server Software is set up to run
· Microsoft is enhancing its server licensing to make it more cost-effective for customers
to utilize Server Software licensed in the Per Processor model when the software, through
partitioning or other similar technology, does not utilize all of the processors in a server.
The URL is:
http://www.microsoft.com/licensing/downloads/Server%20Licensing%20Customer%20Guide.doc
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:%23h6$JawlDHA.1084@.tk2msftngp13.phx.gbl...
> In addition to Allan's answer, the general rule by MS has been that IF the
> procs are on the motherboard (whether or not you have them disabled for SQL
> Server use), you must buy licenses for that proc - or take the proc off of
> the motherboard...
>
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Sarah Kingswell" <sarah.kingswell@.ntlworld.com> wrote in message
> news:#c5oilvlDHA.2592@.TK2MSFTNGP10.phx.gbl...
> > I am going to have to install a web based application on a SQL server that
> > has 4 processors. The web application will integrate with SQL. I do not
> > have any control over the users that access this system. I am assuming I
> > will need to but a 4 processor license for SQL. Is there anyway I can run
> > SQL on just the 1 processor and buy a single processor license?
> >
> >
>|||Hi Tibor...
How have you been doing?
Does that mean that SQL enabled to use 2 procs on an 8 proc machine only
requires 2 proc licenses?
thanks bud, I didn't know that...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:eRxFjtwlDHA.2652@.TK2MSFTNGP09.phx.gbl...
> Hi Wayne!
> > In addition to Allan's answer, the general rule by MS has been that IF
the
> > procs are on the motherboard (whether or not you have them disabled for
SQL
> > Server use), you must buy licenses for that proc - or take the proc off
of
> > the motherboard...
> In the word doc released in May, MS softened down this a bit. Here's a
quote:
> You must acquire licenses for only those processors that are accessible to
any operating system copy
> upon which the Server Software is set up to run
> · Microsoft is enhancing its server licensing to make it more
cost-effective for customers
> to utilize Server Software licensed in the Per Processor model when the
software, through
> partitioning or other similar technology, does not utilize all of the
processors in a server.
>
>
> The URL is:
>
http://www.microsoft.com/licensing/downloads/Server%20Licensing%20Customer%2
0Guide.doc
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
> "Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
> news:%23h6$JawlDHA.1084@.tk2msftngp13.phx.gbl...
> > In addition to Allan's answer, the general rule by MS has been that IF
the
> > procs are on the motherboard (whether or not you have them disabled for
SQL
> > Server use), you must buy licenses for that proc - or take the proc off
of
> > the motherboard...
> >
> >
> >
> > --
> > Wayne Snyder, MCDBA, SQL Server MVP
> > Computer Education Services Corporation (CESC), Charlotte, NC
> > www.computeredservices.com
> > (Please respond only to the newsgroups.)
> >
> > I support the Professional Association of SQL Server (PASS) and it's
> > community of SQL Server professionals.
> > www.sqlpass.org
> >
> >
> > "Sarah Kingswell" <sarah.kingswell@.ntlworld.com> wrote in message
> > news:#c5oilvlDHA.2592@.TK2MSFTNGP10.phx.gbl...
> > > I am going to have to install a web based application on a SQL server
that
> > > has 4 processors. The web application will integrate with SQL. I do
not
> > > have any control over the users that access this system. I am
assuming I
> > > will need to but a 4 processor license for SQL. Is there anyway I can
run
> > > SQL on just the 1 processor and buy a single processor license?
> > >
> > >
> >
> >
>|||My reading of the doc - If the processor is available to the OS, you have to
pay... I'll ask someone at PASS next month... Are you coming?...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:eRxFjtwlDHA.2652@.TK2MSFTNGP09.phx.gbl...
> Hi Wayne!
> > In addition to Allan's answer, the general rule by MS has been that IF
the
> > procs are on the motherboard (whether or not you have them disabled for
SQL
> > Server use), you must buy licenses for that proc - or take the proc off
of
> > the motherboard...
> In the word doc released in May, MS softened down this a bit. Here's a
quote:
> You must acquire licenses for only those processors that are accessible to
any operating system copy
> upon which the Server Software is set up to run
> · Microsoft is enhancing its server licensing to make it more
cost-effective for customers
> to utilize Server Software licensed in the Per Processor model when the
software, through
> partitioning or other similar technology, does not utilize all of the
processors in a server.
>
>
> The URL is:
>
http://www.microsoft.com/licensing/downloads/Server%20Licensing%20Customer%2
0Guide.doc
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
> "Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
> news:%23h6$JawlDHA.1084@.tk2msftngp13.phx.gbl...
> > In addition to Allan's answer, the general rule by MS has been that IF
the
> > procs are on the motherboard (whether or not you have them disabled for
SQL
> > Server use), you must buy licenses for that proc - or take the proc off
of
> > the motherboard...
> >
> >
> >
> > --
> > Wayne Snyder, MCDBA, SQL Server MVP
> > Computer Education Services Corporation (CESC), Charlotte, NC
> > www.computeredservices.com
> > (Please respond only to the newsgroups.)
> >
> > I support the Professional Association of SQL Server (PASS) and it's
> > community of SQL Server professionals.
> > www.sqlpass.org
> >
> >
> > "Sarah Kingswell" <sarah.kingswell@.ntlworld.com> wrote in message
> > news:#c5oilvlDHA.2592@.TK2MSFTNGP10.phx.gbl...
> > > I am going to have to install a web based application on a SQL server
that
> > > has 4 processors. The web application will integrate with SQL. I do
not
> > > have any control over the users that access this system. I am
assuming I
> > > will need to but a 4 processor license for SQL. Is there anyway I can
run
> > > SQL on just the 1 processor and buy a single processor license?
> > >
> > >
> >
> >
>|||Hi Wayne,
> How have you been doing?
I'm good, thanks! Hope you are too :-)
> Does that mean that SQL enabled to use 2 procs on an 8 proc machine only
> requires 2 proc licenses?
Just trimming affinity mask doesn't help, need to be restricted at the OS level (as you posted in
the other post).
> My reading of the doc - If the processor is available to the OS, you have to
> pay... I'll ask someone at PASS next month...
Yep, that is my interpretation as well. Let us know of you get some conflicting info.
> I'll ask someone at PASS next month... Are you coming?...
I'm afraid not. Too much going on here... :-)
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:%23H5Hq$zlDHA.1764@.tk2msftngp13.phx.gbl...
> Hi Tibor...
> How have you been doing?
> Does that mean that SQL enabled to use 2 procs on an 8 proc machine only
> requires 2 proc licenses?
> thanks bud, I didn't know that...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> wrote in message news:eRxFjtwlDHA.2652@.TK2MSFTNGP09.phx.gbl...
> > Hi Wayne!
> >
> > > In addition to Allan's answer, the general rule by MS has been that IF
> the
> > > procs are on the motherboard (whether or not you have them disabled for
> SQL
> > > Server use), you must buy licenses for that proc - or take the proc off
> of
> > > the motherboard...
> >
> > In the word doc released in May, MS softened down this a bit. Here's a
> quote:
> > You must acquire licenses for only those processors that are accessible to
> any operating system copy
> > upon which the Server Software is set up to run
> > · Microsoft is enhancing its server licensing to make it more
> cost-effective for customers
> > to utilize Server Software licensed in the Per Processor model when the
> software, through
> > partitioning or other similar technology, does not utilize all of the
> processors in a server.
> >
> >
> >
> >
> >
> > The URL is:
> >
> http://www.microsoft.com/licensing/downloads/Server%20Licensing%20Customer%2
> 0Guide.doc
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > Archive at: http://groups.google.com/groups?oi=djq&as
> ugroup=microsoft.public.sqlserver
> >
> >
> > "Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
> > news:%23h6$JawlDHA.1084@.tk2msftngp13.phx.gbl...
> > > In addition to Allan's answer, the general rule by MS has been that IF
> the
> > > procs are on the motherboard (whether or not you have them disabled for
> SQL
> > > Server use), you must buy licenses for that proc - or take the proc off
> of
> > > the motherboard...
> > >
> > >
> > >
> > > --
> > > Wayne Snyder, MCDBA, SQL Server MVP
> > > Computer Education Services Corporation (CESC), Charlotte, NC
> > > www.computeredservices.com
> > > (Please respond only to the newsgroups.)
> > >
> > > I support the Professional Association of SQL Server (PASS) and it's
> > > community of SQL Server professionals.
> > > www.sqlpass.org
> > >
> > >
> > > "Sarah Kingswell" <sarah.kingswell@.ntlworld.com> wrote in message
> > > news:#c5oilvlDHA.2592@.TK2MSFTNGP10.phx.gbl...
> > > > I am going to have to install a web based application on a SQL server
> that
> > > > has 4 processors. The web application will integrate with SQL. I do
> not
> > > > have any control over the users that access this system. I am
> assuming I
> > > > will need to but a 4 processor license for SQL. Is there anyway I can
> run
> > > > SQL on just the 1 processor and buy a single processor license?
> > > >
> > > >
> > >
> > >
> >
> >
>

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

Processor license

Hello everyone,
What is the procedure of changing a SQL 2000 server to processor mode
from per seat?
Thank you
Alex AndersonThe following is unsupported but you may want to check the
link:
Q:How to change the license mode after SQL2000 setup?
http://www.tkdinesh.com/faq/ans/license.html
-Sue
On Mon, 23 Aug 2004 15:18:14 -0700, "Alex Anderson"
<AAnderson@.Murrieta.org> wrote:

>Hello everyone,
> What is the procedure of changing a SQL 2000 server to processor mode
>from per seat?
>Thank you
>Alex Anderson
>|||Sue,
Interesting link, however Mode is already set to 0 and I'm running
Windows 2003 Server. Although, contained within the same registry key is a
FlipAllow and I'm not sure what this is used for. Perhaps to allow the
switch between Per device and Processor? I have the licenses for two
processes (just purchased them from Microsoft) and now from what I'm told I
might just have to pay for support to re-license SQL. Go figure...
Thank you
Alex Anderson
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:fe6li09llida0kiqg7tksh26hta255i5de@.
4ax.com...
> The following is unsupported but you may want to check the
> link:
> Q:How to change the license mode after SQL2000 setup?
> http://www.tkdinesh.com/faq/ans/license.html
> -Sue
> On Mon, 23 Aug 2004 15:18:14 -0700, "Alex Anderson"
> <AAnderson@.Murrieta.org> wrote:
>
>

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

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

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

Process license ?

Hello Everyone,
Our company is currently under the Enterprise agreement with Microsoft
and I was wondering when it came to clustering, how many processors do we
have to licenses if both boxes has four processors in each box? The way
we're running the cluster is Active/Passive. We are using SQL 2000 Standard
edition along with Enterprise edition of Microsoft Windows 2003 Server. If
someone could give me some insight I would highly appreciate it.
Thank you
Alex AndersonSQL Server 2000 Standard Edition doesn't support clustering, so that is your
first problem. Now ignoring that, in an Active/Passive configuration you
need only license the maximum number of processors on any server in that
configuration. In your case that would mean 4. If you had a configuration
where the usually active system had 4 and the usually passive system had 8
then you'd need to license 8.
Hal Berenson, President
PredictableIT, LLC
http://www.predictableit.com
"Alex Anderson" <AAnderson@.Murrieta.org> wrote in message
news:usdeZCoJGHA.668@.TK2MSFTNGP11.phx.gbl...
> Hello Everyone,
> Our company is currently under the Enterprise agreement with Microsoft
> and I was wondering when it came to clustering, how many processors do we
> have to licenses if both boxes has four processors in each box? The way
> we're running the cluster is Active/Passive. We are using SQL 2000
> Standard edition along with Enterprise edition of Microsoft Windows 2003
> Server. If someone could give me some insight I would highly appreciate
> it.
> Thank you
> Alex Anderson
>
>|||Alex Anderson wrote:

> Hello Everyone,
> Our company is currently under the Enterprise agreement with Microsoft
> and I was wondering when it came to clustering, how many processors do we
> have to licenses if both boxes has four processors in each box? The way
> we're running the cluster is Active/Passive. We are using SQL 2000 Standa
rd
> edition along with Enterprise edition of Microsoft Windows 2003 Server. I
f
> someone could give me some insight I would highly appreciate it.
> Thank you
> Alex Anderson
SQL Server 2000 Standard Edition doesn't support failover clustering.
Your options are to upgrade to Enterprise Edition or to SQL Server 2005
Standard Edition, which do both support clustering.
"Under each of these editions, keeping a passive server for failover
purposes does not require a license as long as the passive server has
the same or fewer processors than the active server (under the per
processor scenario)."
http://www.microsoft.com/sql/howtobuy/faq.mspx
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||Thank you both. Understood!
Alex Anderson
"Alex Anderson" <AAnderson@.Murrieta.org> wrote in message
news:usdeZCoJGHA.668@.TK2MSFTNGP11.phx.gbl...
> Hello Everyone,
> Our company is currently under the Enterprise agreement with Microsoft
> and I was wondering when it came to clustering, how many processors do we
> have to licenses if both boxes has four processors in each box? The way
> we're running the cluster is Active/Passive. We are using SQL 2000
> Standard edition along with Enterprise edition of Microsoft Windows 2003
> Server. If someone could give me some insight I would highly appreciate
> it.
> Thank you
> Alex Anderson
>
>

Process license ?

Hello Everyone,
Our company is currently under the Enterprise agreement with Microsoft
and I was wondering when it came to clustering, how many processors do we
have to licenses if both boxes has four processors in each box? The way
we're running the cluster is Active/Passive. We are using SQL 2000 Standard
edition along with Enterprise edition of Microsoft Windows 2003 Server. If
someone could give me some insight I would highly appreciate it.
Thank you
Alex AndersonSQL Server 2000 Standard Edition doesn't support clustering, so that is your
first problem. Now ignoring that, in an Active/Passive configuration you
need only license the maximum number of processors on any server in that
configuration. In your case that would mean 4. If you had a configuration
where the usually active system had 4 and the usually passive system had 8
then you'd need to license 8.
--
Hal Berenson, President
PredictableIT, LLC
http://www.predictableit.com
"Alex Anderson" <AAnderson@.Murrieta.org> wrote in message
news:usdeZCoJGHA.668@.TK2MSFTNGP11.phx.gbl...
> Hello Everyone,
> Our company is currently under the Enterprise agreement with Microsoft
> and I was wondering when it came to clustering, how many processors do we
> have to licenses if both boxes has four processors in each box? The way
> we're running the cluster is Active/Passive. We are using SQL 2000
> Standard edition along with Enterprise edition of Microsoft Windows 2003
> Server. If someone could give me some insight I would highly appreciate
> it.
> Thank you
> Alex Anderson
>
>|||Alex Anderson wrote:
> Hello Everyone,
> Our company is currently under the Enterprise agreement with Microsoft
> and I was wondering when it came to clustering, how many processors do we
> have to licenses if both boxes has four processors in each box? The way
> we're running the cluster is Active/Passive. We are using SQL 2000 Standard
> edition along with Enterprise edition of Microsoft Windows 2003 Server. If
> someone could give me some insight I would highly appreciate it.
> Thank you
> Alex Anderson
SQL Server 2000 Standard Edition doesn't support failover clustering.
Your options are to upgrade to Enterprise Edition or to SQL Server 2005
Standard Edition, which do both support clustering.
"Under each of these editions, keeping a passive server for failover
purposes does not require a license as long as the passive server has
the same or fewer processors than the active server (under the per
processor scenario)."
http://www.microsoft.com/sql/howtobuy/faq.mspx
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||Thank you both. Understood!
Alex Anderson
"Alex Anderson" <AAnderson@.Murrieta.org> wrote in message
news:usdeZCoJGHA.668@.TK2MSFTNGP11.phx.gbl...
> Hello Everyone,
> Our company is currently under the Enterprise agreement with Microsoft
> and I was wondering when it came to clustering, how many processors do we
> have to licenses if both boxes has four processors in each box? The way
> we're running the cluster is Active/Passive. We are using SQL 2000
> Standard edition along with Enterprise edition of Microsoft Windows 2003
> Server. If someone could give me some insight I would highly appreciate
> it.
> Thank you
> Alex Anderson
>
>

Process license ?

Hello Everyone,
Our company is currently under the Enterprise agreement with Microsoft
and I was wondering when it came to clustering, how many processors do we
have to licenses if both boxes has four processors in each box? The way
we're running the cluster is Active/Passive. We are using SQL 2000 Standard
edition along with Enterprise edition of Microsoft Windows 2003 Server. If
someone could give me some insight I would highly appreciate it.
Thank you
Alex Anderson
SQL Server 2000 Standard Edition doesn't support clustering, so that is your
first problem. Now ignoring that, in an Active/Passive configuration you
need only license the maximum number of processors on any server in that
configuration. In your case that would mean 4. If you had a configuration
where the usually active system had 4 and the usually passive system had 8
then you'd need to license 8.
Hal Berenson, President
PredictableIT, LLC
http://www.predictableit.com
"Alex Anderson" <AAnderson@.Murrieta.org> wrote in message
news:usdeZCoJGHA.668@.TK2MSFTNGP11.phx.gbl...
> Hello Everyone,
> Our company is currently under the Enterprise agreement with Microsoft
> and I was wondering when it came to clustering, how many processors do we
> have to licenses if both boxes has four processors in each box? The way
> we're running the cluster is Active/Passive. We are using SQL 2000
> Standard edition along with Enterprise edition of Microsoft Windows 2003
> Server. If someone could give me some insight I would highly appreciate
> it.
> Thank you
> Alex Anderson
>
>
|||Alex Anderson wrote:

> Hello Everyone,
> Our company is currently under the Enterprise agreement with Microsoft
> and I was wondering when it came to clustering, how many processors do we
> have to licenses if both boxes has four processors in each box? The way
> we're running the cluster is Active/Passive. We are using SQL 2000 Standard
> edition along with Enterprise edition of Microsoft Windows 2003 Server. If
> someone could give me some insight I would highly appreciate it.
> Thank you
> Alex Anderson
SQL Server 2000 Standard Edition doesn't support failover clustering.
Your options are to upgrade to Enterprise Edition or to SQL Server 2005
Standard Edition, which do both support clustering.
"Under each of these editions, keeping a passive server for failover
purposes does not require a license as long as the passive server has
the same or fewer processors than the active server (under the per
processor scenario)."
http://www.microsoft.com/sql/howtobuy/faq.mspx
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
|||Thank you both. Understood!
Alex Anderson
"Alex Anderson" <AAnderson@.Murrieta.org> wrote in message
news:usdeZCoJGHA.668@.TK2MSFTNGP11.phx.gbl...
> Hello Everyone,
> Our company is currently under the Enterprise agreement with Microsoft
> and I was wondering when it came to clustering, how many processors do we
> have to licenses if both boxes has four processors in each box? The way
> we're running the cluster is Active/Passive. We are using SQL 2000
> Standard edition along with Enterprise edition of Microsoft Windows 2003
> Server. If someone could give me some insight I would highly appreciate
> it.
> Thank you
> Alex Anderson
>
>