Changing number of per processor licenses

I want to change the number of licenses from 2 to 1 so I can use one license
on another machine. To accomplish this, do I need to physically remove the
CPU or I can unselect 1 processor from the Processor Tab of properties sheet
.You would violate license agreement by only unselecting one processor from E
M's config dialog. The
license terms states you need one proc license per processor that the OS can
use. So either disable
one processor in BIOS (if possible) or remove it.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"SB138" <SB138@.discussions.microsoft.com> wrote in message
news:0768CDED-D7D6-4E3F-8450-25B56D297A64@.microsoft.com...[vbcol=seagreen]
>I want to change the number of licenses from 2 to 1 so I can use one licens
e
> on another machine. To accomplish this, do I need to physically remove the
> CPU or I can unselect 1 processor from the Processor Tab of properties sheet.[/vbc
ol]

Changing number of per processor licenses

I want to change the number of licenses from 2 to 1 so I can use one license
on another machine. To accomplish this, do I need to physically remove the
CPU or I can unselect 1 processor from the Processor Tab of properties sheet.
You would violate license agreement by only unselecting one processor from EM's config dialog. The
license terms states you need one proc license per processor that the OS can use. So either disable
one processor in BIOS (if possible) or remove it.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"SB138" <SB138@.discussions.microsoft.com> wrote in message
news:0768CDED-D7D6-4E3F-8450-25B56D297A64@.microsoft.com...
>I want to change the number of licenses from 2 to 1 so I can use one license
> on another machine. To accomplish this, do I need to physically remove the
> CPU or I can unselect 1 processor from the Processor Tab of properties sheet.

Changing number of per processor licenses

I want to change the number of licenses from 2 to 1 so I can use one license
on another machine. To accomplish this, do I need to physically remove the
CPU or I can unselect 1 processor from the Processor Tab of properties sheet.You would violate license agreement by only unselecting one processor from EM's config dialog. The
license terms states you need one proc license per processor that the OS can use. So either disable
one processor in BIOS (if possible) or remove it.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"SB138" <SB138@.discussions.microsoft.com> wrote in message
news:0768CDED-D7D6-4E3F-8450-25B56D297A64@.microsoft.com...
>I want to change the number of licenses from 2 to 1 so I can use one license
> on another machine. To accomplish this, do I need to physically remove the
> CPU or I can unselect 1 processor from the Processor Tab of properties sheet.

Changing Licensing Model on production server

Hello All,
I have a pre-existing SQL server that appears to have been installed with
the incorrect licensing model (ie CAL/Per-Seat vs Processor). As such I need
to change the licensing model on the server to reflect the proper licensing
configuration that is in place.
Is there a way that this can ben done absent of having to reinstall SQL?
Thanks!
Licensing should'nt affect QSL Operation; if you change from CAL to
Processor, just verify that the number of concurrent connections (Server
properties - Connections) arises to 0; eventually reset manually that value.
Passing from Processor to CAL you should set the same value to the right
value.
Remember however that the respect of your licensing option is something the
YOU and Microsoft agreed, and is'nt controlled by some software feature.
To be completely advised about licensing terms i suggest a call to your
Microsoft representative.
Gilberto Zampatti
"DBADave" wrote:

> Hello All,
> I have a pre-existing SQL server that appears to have been installed with
> the incorrect licensing model (ie CAL/Per-Seat vs Processor). As such I need
> to change the licensing model on the server to reflect the proper licensing
> configuration that is in place.
> Is there a way that this can ben done absent of having to reinstall SQL?
> Thanks!
|||Thanks Gilberto,
Specifically I need to know how I can change the licensing model from CAL to
Processor within Control Panel, as by default there is no option to switch
between the 2 modes. I understand that outside of reinstalling SQL, there
may be a registry change that is required and am interested to understand
what registry change (or alternate method other then reinstalling) can be
employed.
Thanks,
Dave
"Gilberto Zampatti" wrote:
[vbcol=seagreen]
> Licensing should'nt affect QSL Operation; if you change from CAL to
> Processor, just verify that the number of concurrent connections (Server
> properties - Connections) arises to 0; eventually reset manually that value.
> Passing from Processor to CAL you should set the same value to the right
> value.
> Remember however that the respect of your licensing option is something the
> YOU and Microsoft agreed, and is'nt controlled by some software feature.
> To be completely advised about licensing terms i suggest a call to your
> Microsoft representative.
> Gilberto Zampatti
> "DBADave" wrote:

Changing Licensing Model on production server

Hello All,
I have a pre-existing SQL server that appears to have been installed with
the incorrect licensing model (ie CAL/Per-Seat vs Processor). As such I need
to change the licensing model on the server to reflect the proper licensing
configuration that is in place.
Is there a way that this can ben done absent of having to reinstall SQL?
Thanks!Licensing should'nt affect QSL Operation; if you change from CAL to
Processor, just verify that the number of concurrent connections (Server
properties - Connections) arises to 0; eventually reset manually that value.
Passing from Processor to CAL you should set the same value to the right
value.
Remember however that the respect of your licensing option is something the
YOU and Microsoft agreed, and is'nt controlled by some software feature.
To be completely advised about licensing terms i suggest a call to your
Microsoft representative.
Gilberto Zampatti
"DBADave" wrote:
> Hello All,
> I have a pre-existing SQL server that appears to have been installed with
> the incorrect licensing model (ie CAL/Per-Seat vs Processor). As such I need
> to change the licensing model on the server to reflect the proper licensing
> configuration that is in place.
> Is there a way that this can ben done absent of having to reinstall SQL?
> Thanks!|||Thanks Gilberto,
Specifically I need to know how I can change the licensing model from CAL to
Processor within Control Panel, as by default there is no option to switch
between the 2 modes. I understand that outside of reinstalling SQL, there
may be a registry change that is required and am interested to understand
what registry change (or alternate method other then reinstalling) can be
employed.
Thanks,
Dave
"Gilberto Zampatti" wrote:
> Licensing should'nt affect QSL Operation; if you change from CAL to
> Processor, just verify that the number of concurrent connections (Server
> properties - Connections) arises to 0; eventually reset manually that value.
> Passing from Processor to CAL you should set the same value to the right
> value.
> Remember however that the respect of your licensing option is something the
> YOU and Microsoft agreed, and is'nt controlled by some software feature.
> To be completely advised about licensing terms i suggest a call to your
> Microsoft representative.
> Gilberto Zampatti
> "DBADave" wrote:
> > Hello All,
> >
> > I have a pre-existing SQL server that appears to have been installed with
> > the incorrect licensing model (ie CAL/Per-Seat vs Processor). As such I need
> > to change the licensing model on the server to reflect the proper licensing
> > configuration that is in place.
> >
> > Is there a way that this can ben done absent of having to reinstall SQL?
> >
> > Thanks!

Changing Licensing Model on production server

Hello All,
I have a pre-existing SQL server that appears to have been installed with
the incorrect licensing model (ie CAL/Per-Seat vs Processor). As such I nee
d
to change the licensing model on the server to reflect the proper licensing
configuration that is in place.
Is there a way that this can ben done absent of having to reinstall SQL?
Thanks!Licensing should'nt affect QSL Operation; if you change from CAL to
Processor, just verify that the number of concurrent connections (Server
properties - Connections) arises to 0; eventually reset manually that value.
Passing from Processor to CAL you should set the same value to the right
value.
Remember however that the respect of your licensing option is something the
YOU and Microsoft agreed, and is'nt controlled by some software feature.
To be completely advised about licensing terms i suggest a call to your
Microsoft representative.
Gilberto Zampatti
"DBADave" wrote:

> Hello All,
> I have a pre-existing SQL server that appears to have been installed with
> the incorrect licensing model (ie CAL/Per-Seat vs Processor). As such I n
eed
> to change the licensing model on the server to reflect the proper licensin
g
> configuration that is in place.
> Is there a way that this can ben done absent of having to reinstall SQL?
> Thanks!|||Thanks Gilberto,
Specifically I need to know how I can change the licensing model from CAL to
Processor within Control Panel, as by default there is no option to switch
between the 2 modes. I understand that outside of reinstalling SQL, there
may be a registry change that is required and am interested to understand
what registry change (or alternate method other then reinstalling) can be
employed.
Thanks,
Dave
"Gilberto Zampatti" wrote:
[vbcol=seagreen]
> Licensing should'nt affect QSL Operation; if you change from CAL to
> Processor, just verify that the number of concurrent connections (Server
> properties - Connections) arises to 0; eventually reset manually that valu
e.
> Passing from Processor to CAL you should set the same value to the right
> value.
> Remember however that the respect of your licensing option is something th
e
> YOU and Microsoft agreed, and is'nt controlled by some software feature.
> To be completely advised about licensing terms i suggest a call to your
> Microsoft representative.
> Gilberto Zampatti
> "DBADave" wrote:
>