SQL Server 2000 Licensing Question
-
I have a query with regard to SQL Server licensing (which has always been a bit of a grey area to me to be honest
)I have been informed that on one of our servers that we have a Single processor license of SQL Server. It is my understanding that the edition is Standard
I have recently discovered that the Server has 2 processors.
First is there such a thing as a single processor license, second how can we tell what the licensing is. Can we just change the configuration in EM to change the number of processors to use all available
Thanks
-
For per-processor licensing, you license only the processors you use, not the number of processors in the box. You can choose to license some or all of the processors in the computer.
To set the number of processors used, fire up Enterprise Manager, right-click your server, and choose Properties.
From the server properties dialog, click the 'Processor' tab. You should see an entry for every processor on the system. If you have a one-processor license, select one of the processors, and click 'OK'.
Note: hyper-threaded and dual-core processors count as a single processor with thier parent processor. For example, if you have a 2-processor server with hyperthreading enabled, there will be four processors showing in the processor list. A single processor license allows you to select a physical processor and its associated hyperthreaded processor. You're on your own for figuring out which is which. Same for dual-core processors: a processor license is good for running SQL Server on both cores of a single processor.
-Eddie
Eddie Wuerch
MCM: SQL -
Simon,
Eddie is correct, you can see 2 processors on the Processor tab in SQL Server Properties and 2 processors in System Summary but it could be only 1 physical processor. You need to ask your server support
Also read:
http://www.microsoft.com/sql/howtobuy/multicore.mspx
SQL Server Multicore Licensing Policy
It says: "...
Microsoft has been driving thought leadership in this area by charging the same amount per processor, regardless of how many cores are in the processor. Microsoft was the first database vendor to make this announcement, in October of 2004, and continues to be the only vendor to date that has taken this position. This strategy is based on the belief that multicore processors are a natural extension of Moore's Law (that the number of transistors on a chip doubles about every one to two years), and that the benefits should be passed on directly to customers...."
Regards,Yelena Varsha
-
Thanks for that Yelena and Eddie. I'd known about the hyperthreading scenario with twice the numver of processors being shown, but that's giving me some useful background as to why it shows double - cheers.
How simple is it to change to a per server license rather than per processor (I note that on all of our other installations the "Use all available processors" radio button is selected)
And If I do change, is a re-install required (as I believe is the case when switching between per seat and per server licensing) or is it simply a question of buying the correct license and then clicking on the "use all available processors" radio button in EM and ensuring that all available processors are selected ?
-
Simon,
Per server license I think requires re-install to change from Per Processor, but it all depends on your corporate agreement. Per server license suggests you need per user or per device additional licenses that cover the number of users or connected clients respectively. You would buy per server + CALs (Client Access Licenses) only if you have just several users. Typically Microsoft requires Per Processor if you are running a Web application. The only exclusion could be if you corporate agreement covers your client licences and only internal users use the application. But then , again, corporate still paying for CALs. You have to check if your company has any agreements with Microsoft.
Yelena
Regards,Yelena Varsha
-
Note:
Restricting SQL to certain CPUs (by "affinity mask") does not affect the licensing required.
The CPUs must be not visible to the OS and unavailable for the OS: disabled in the BIOS or not there.
http://www.microsoft.com/sql/howtobuy/faq.mspx
Q. Do I have to license all of the processors in a server? A. You only have to acquire licenses for processors that are accessible to any copy of the operating system upon which SQL Server 2000 is installed.
There is a good chance the box has one CPU but hyperthreaded or dual core anyway
-
Thanks for that Yelena and Shawn,
Yelena, we are using the server in for a Web application, so that obviously explains the per processor licensing agreement that was purchased.
One of the things that triggered this query off was out IT manager going through the SQL licensing agreements and noticing that the per processor license that had been purchased was significantly more expensive than the SQL server standard per server licenses that had been purchased...and to our logic without knowing the intricacies of SQL Server licensing, it looked odd that it cost less for a standard per-server license where we are not limitting the number of processors compared to a per processor license
Incidentally as a side issue, why would one choose to limit the number of processors used by going through EM and manually deselecting some of them - are there any scenarios that you could think of
Cheers
Simon
-
Sorry
just noticed that I was referring to Per "Server Licensing" when it was killed off after SQL 7
-
There are some ideas around about using affinity mask (which is effectively what you do in EM) but I've never needed to change it. There is a lot of noise and ill concieved ideas about changing various advanced settings, but never change anything without verifying you need to.
If your web box is on an intranet, then you can use "Server/CAL", because you can quantify and identify your MSSQL client base. On the internet, "per-processor" is your only option.
-
The classic scenario for Affinity Mask from MSDN: when you have a network traffic on the server and the network card gets the highest numbered processor, next network card gets next available highest numbered processor. In this scenario you would limit SQL Server to the lowest numbered processors for performance.
Read:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_config_6rw2.asp
affinity mask Option
Regards,Yelena Varsha
-
Hi Yelena and Shawn,
Much appreciated, you've both been a great help
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply