Standard version on 2 (quad core) cpu with 16 Gb RAM

  • We are implementing a sql server with:

    2 (quad core) cpu

    16 Gb Ram

    Windows 2003 Enterprise (to use +4GB RAM)

    SQL 2005 standard version

    Will standard version do/work or is there a need for enterprise version?

    thanks, Jac

  • Per Microsoft, Standard Edition can use as much RAM as the OS will give it.

    http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • Okay, thats for the RAM.

    And for the CPU: The limit for the standard version is 4 cpu's.

    Wil it use both CPU's or only one CPU (with the quad core)

    And what about the licence's needed.

    Jac

  • Microsoft licenses and checks sockets, not cores. SQL will use all 8 cores, you'll need 2CPU licenses if you go that way.

  • The license and limit is per CPU, not per core, so 2 quad-cores can be licensed and used as 2 CPUs. Microsoft is reviewing that as more and more cores get tied onto single CPUs (8-core CPUs and 16-core CPUs exist, but I don't think they're in use in Windows servers yet).

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • So that is: the 4 cpu limit in the standard version addresses 4 physical cpu (e.g. 16 core).

    I can use:

    1 cpu (4core) and need 1 licence

    2 cpu (8 core) and need 2 licence

    and so on??

    Jac

  • Exactly.

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • Depends whether you're going for per CPU or per seat licencing. Per CPU licences are a lot more expensive, so if you don't have a large number of users, consider licencing per seat.

    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

Viewing 8 posts - 1 through 7 (of 7 total)

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