Processor based SQL server license

  • I tried to figure out some license question for per processor based license.

    I found out one of our SQL servers processor information by doing this:

    1. use cmd, type systeminfo

    2. I see :

    System Manufacturer: HP

    System Model: ProLiant DL380 G4

    System Type: x64-based PC

    Processor(s): 2 Processor(s) Installed.

    [01]: Intel64 Family 15 Model 4 Stepping 3 GenuineInt

    el ~2800 Mhz

    [02]: Intel64 Family 15 Model 4 Stepping 3 GenuineInt

    Does this mean we have to buy two licenses if SQL server installed on the server?

    I know when we bought license we just bought one process license.

    Thanks,

  • According to HP.com, the only 2.8GHz processor for DL380 G4 is a dual core processor. So, if that is right you have a single physical processor, and only need one processor license.



    Ole Kristian Velstadbråten Bangås - Virinco - Facebook - Twitter

    Concatenating Row Values in Transact-SQL[/url]

  • Using something like WMIExplorer you could look at the Win32_Processor class and the number of instances there will be the number of processors, within that class you can see cores and logical processors.

    Or you can look at Win32_Computersystem the NumberOfProcessors attribute will also tell you.

    I would say that is extremely reliable.

    CEWII

  • I don't have wmiexplorer tool, is there an easy way to find how many physical processors ?

    I did a search and found a one that queries SQL, but I would like to find one before we install SQL server.

    SQL one:

    EXEC xp_instance_regread

    'HKEY_LOCAL_MACHINE',

    'HARDWARE\DESCRIPTION\System\CentralProcessor\0',

    'ProcessorNameString';

    SELECT cpu_count AS [Logical CPU Count], hyperthread_ratio AS [Hyperthread Ratio],

    cpu_count/hyperthread_ratio AS [Physical CPU Count]

    FROM sys.dm_os_sys_info OPTION (RECOMPILE);

  • WMIExplorer:

    http://www.ks-soft.net/hostmon.eng/wmi/index.htm

    CEWII

  • I found out one of our SQL servers processor information by doing this:

    1. use cmd, type systeminfo

    I assume that this server is running some version of Windows Server. If so, then just right-click on Computer in the Start Menu and select properties.

    When I do this on my PC, I see something like this:

    Intel Core2 Duo CPU E800 @ 3.33 GHz, 3.33 GHz

    That's one processor with two cores. I'll bet you'll see something similar.

  • I see from right click system-property,

    Processor: Intel(R)Xeon(TM) CPU 3.60GHz 3.60GHz(2 Processors)

    Does this mean if I install SQL server on it, I need to buy two Processor licenses, that's expensive:angry:

  • sqlfriends (10/21/2011)


    I see from right click system-property,

    Processor: Intel(R)Xeon(TM) CPU 3.60GHz 3.60GHz(2 Processors)

    Does this mean if I install SQL server on it, I need to buy two Processor licenses, that's expensive:angry:

    Sorry, in this case, that is two processors. (Each processor will have multiple cores.)

    You need two processor licenses. :ermm:

  • And if you can't/won't buy a second licence, you need to disable that processor in the BIOS so that windows can't see it. Setting affinity is not enough.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Thanks,

    So when I plan my next server, what is the best to do for hardware also considering the price of license.

    What you do as DBA, to plan for your hardware, I know the answer maybe it depends.

    But for regular mid size databases, what you plan for order for hardware:

    1 processor duel core, quad core

    2 processors, or etc

    Thanks

  • Depends on budget, expected load, operational policies, deprecation cycle, etc.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Well, you are right: it depends. However, here is one thought. Buy the beefiest server you can wrangle out of your employer's (hopefully) deep pockets, and then virtualize.

    If you can guarantee, for example, that your virtual SQL server is nailed to one physical processor, then you only need one processor license. Also, the higher editions of SQL server (like Enterprise or Datacenter editions) allow you to install the software on more than one virtual operating system environment (as long as they are on the same physical server).

    As always, consult the Product Use Rights document:

    http://www.microsoft.com/licensing/about-licensing/product-licensing.aspx

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply