SQL SERVER 2005 Per Processor Licensing Question

[sanjdhiman]

Hi

I have a virtual Box where i want to build a SQL Server 2005 instance. This is going to be licensed using per processor licensing. currently starting at 2 processors.

How easy is it to tell SQL SERVER 2005 to use additional CPUs if I change the processors to 6 processors on the box.

i.e. moving from 2 CPUs to 6 CPUs, is it a simple case of making the CPUs available to the server and then checking under Properties-->Processors each extra CPU I want to use?

I would then naturally tell Microsoft that i have uped the number of CPUs being used.

So question is how easy is it to add more processors to the box and making those processors available to SQL SERVER,

Thanks

Sanj

 

[Crowley16]

this is probably a redundant question but I just want to make sure...

it's actual processors you're talking about and not cores right?

--------------------
Procrastinate Now!

 

[sanjdhiman]

yep
the processors have 4 cores each, so yep Microsoft still charge per CPU not per core.

Is it possible to add more CPUs and then tell SQL SERVER 2005 to use the extra CPUS at a later stage?

 

[onpnt]

From my understanding if SQL Server is installed on a server it MUST have a license for every physical processor that is present no matter if you use it or not.

And of course that does not include cores only the proc

I don't know VM details and to be honest don't recommend using it for SQL Server so I may be wrong

[sub]____________ signature below ______________
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]

 

[Crowley16]

well, I don't have 2005 to confirm this, however you can add new processors with 2000 so I would guess that it'd be the same with 2005

--------------------
Procrastinate Now!

 

[mrdenny]

If adding processors you have to license all the physical CPUs in the machine reguardless of how many you actually use.

If you are going to add CPUs to a SQL Server it should pick them up automatically.

SQL Server typically isn't a good candidate for virtulizing. It takes to many resources from the host VMWare system. It would be better to have a physical server for the SQL Server and a VMWare enviroment for the rest of the appliction systems.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[sanjdhiman]

thanks guys for the info.

My apologise with regards to VM ware . What I meant was Virtual Processors. I.e. 1CPU has 4 cores aka 4 Virtual Processors. Bad terminology, I know.

I wouldnt ever dream of putting SQL SErver on a VMWare system.

Apologise

Ok so thanks for the licensing info

 

[mrdenny]

In that case all you do is drop in the new CPUs are buy the licenses and you should be good to go. As I said above by default SQL will pick up the new CPUs automatically.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com