By: Svetlana Golovko | Comments (41) | Related: > Licensing
Problem
With SQL Server 2012, Microsoft introduced a new licensing model; licensing per core replaced the licensing per processor. We need to adjust budget to reflect licensing changes for our next Enterprise Agreement renewal, but we do not have processor core information from any of our server inventory tools. How can we quickly gather information about each server's processor cores without logging in to each server?
Solution
In this tip we will provide a PowerShell script that you can use to query your servers for the number of processors (CPUs) and cores. The entire licensing process is more complicated than just the number of CPUs or cores (you have to take into consideration SQL Server edition and virtualization), but this script is a good start.
If you are not familiar with the SQL Server 2012 licensing model changes you can read this tip. This tip describes the licensing changes and also it has several useful links to Microsoft documentation.
PowerShell Function to Find Number of SQL Server Processors and Cores
We will create a PowerShell function that utilizes Win32_Processor and Win32_ComputerSystem WMI classes. The function accepts ComputerName as a parameter that can be piped from a text file.
param([string]$SQLServerList=$(Throw `
"Paramater missing: -SQLServerList ConfigGroup"))
Function Get-CPUInfo{
[CmdletBinding()]
Param(
[parameter(Mandatory = $TRUE,ValueFromPipeline = $TRUE)] [String] $ServerName
)
Process{
# Get Default SQL Server instance's Edition
$sqlconn = new-object System.Data.SqlClient.SqlConnection(`
"server=$ServerName;Trusted_Connection=true");
$query = "SELECT SERVERPROPERTY('Edition') AS Edition, SERVERPROPERTY('MachineName') AS MachineName;"
$sqlconn.Open()
$sqlcmd = new-object System.Data.SqlClient.SqlCommand ($query, $sqlconn);
$sqlcmd.CommandTimeout = 0;
$dr = $sqlcmd.ExecuteReader();
while ($dr.Read()) {
$SQLEdition = $dr.GetValue(0);
$MachineName = $dr.GetValue(1);}
$dr.Close()
$sqlconn.Close()
#Get processors information
$CPU=Get-WmiObject -ComputerName $MachineName -class Win32_Processor
#Get Computer model information
$OS_Info=Get-WmiObject -ComputerName $MachineName -class Win32_ComputerSystem
#Reset number of cores and use count for the CPUs counting
$CPUs = 0
$Cores = 0
foreach($Processor in $CPU){
$CPUs = $CPUs+1
#count the total number of cores
$Cores = $Cores+$Processor.NumberOfCores
}
$InfoRecord = New-Object -TypeName PSObject -Property @{
Server = $ServerName;
Model = $OS_Info.Model;
CPUNumber = $CPUs;
TotalCores = $Cores;
Edition = $SQLEdition;
'Cores to CPUs Ratio' = $Cores/$CPUs;
Resume = if ($SQLEdition -like "Developer*") {"N/A"} `
elseif ($Cores -eq $CPUs) {"No licensing changes"} `
else {"licensing costs increase in " + $Cores/$CPUs +" times"};
}
Write-Output $InfoRecord
}
}
#loop through the server list and get information about CPUs, Cores and Default instance edition
Get-Content $SQLServerList | Foreach-Object {Get-CPUInfo $_ }|Format-Table -AutoSize Server, Model, Edition, CPUNumber, TotalCores, 'Cores to CPUs Ratio', ResumeSave the script as "Cores_to_CPU_Ratio.ps1" PowerShell file.
Running the PowerShell script to Find Number of Cores and Processors
The script requires a list of SQL Servers as the input parameter. This could just be a simple text file with one column (without a column header) containing host names only. You do not use the SQL Server named instance, because we want to look at the physical box.
Use the "SL" command to change to the directory where you saved the script and run the script as shown below:
SL "M:\DBA\Scripts\powerShell" .\Cores_to_CPU_Ratio.ps1 -SQLServerList "C:\SQLSrvList1.txt"
Here are the results for the demo environment:
Interpreting the results for the Number of Processors and Cores
The information about potential licensing is in the "Resume" column. If we have the same number of CPUs as number of Cores then we do not have to worry about licensing more cores.
Another set of useful information could be obtained analyzing "Model", "Edition" and "Ratio" columns. In our example we have more than 50% of our SQL Servers on VMware. Most of them are Enterprise Edition. We also have DEMOSRV5 which is a physical server where we will see the highest increase in licensing costs. Based on this information we can see that it would be beneficial to migrate DEMOSRV5 to a virtual server and to take advantage of the Maximum Virtualization licensing. Note, you can only take advantage of this if you have Software Assurance (SA) coverage. Read more about Microsoft SQL Server 2012 Virtualization Licensing here.
Next Steps
- Read more PowerShell tips here.
- Read Microsoft's "Determining SQL Server 2012 Core Licensing Requirements at SA Renewal" document.
- Read Microsoft's "SQL Server 2012 Licensing Guide" document.
- Use the script to assess your environment if you have not transitioned yet to the new licensing model or use it just to review your current environment. You will need to take into consideration the highest Edition installed on your server. For example, if you have Standard and Enterprise Edition installed on the same server as different SQL Server instances you will need to apply Enterprise licensing for that server.
- Use this script to find out if you can take advantage of the Maximum Virtualization licensing mode.
About the author
Svetlana Golovko is a DBA with 13 years of the IT experience (including SQL Server and Oracle) with main focus on performance. This author pledges the content of this article is based on professional experience and not AI generated.
View all my tips
