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

Changing Licenses

We have a situation where we need to change instances from CAL to Proc on
Enterprise Edition instances. If we purchase the Proc licenses without
actually making the conversion, will this be a problem? Or do we need to
physically convert the license? I understand it is an honor system, but I
want to make sure that we have properly reported our licenses and done them
correctly. I also was told that in order to convert the licenses we had to
reinstall the instance. Is this true?
Thanks for any assistance.I'm disagree with the comment you needed to install your stuff all over
again.
According to my opinion there is nothing you are gonna do about this license
changing thing. You just need your new license.
However, I encourage you to consult an authorized vendor to be sure and to
know about the process of this transition.
--
Ekrem Ã?nsoy
"Cheetah2399" <Cheetah2399@.discussions.microsoft.com> wrote in message
news:D6A1E9F0-1637-417C-AD8D-B21D3EF7DA5F@.microsoft.com...
> We have a situation where we need to change instances from CAL to Proc on
> Enterprise Edition instances. If we purchase the Proc licenses without
> actually making the conversion, will this be a problem? Or do we need to
> physically convert the license? I understand it is an honor system, but I
> want to make sure that we have properly reported our licenses and done
> them
> correctly. I also was told that in order to convert the licenses we had
> to
> reinstall the instance. Is this true?
> Thanks for any assistance.