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: