How does licensing work for SQL Server that powers a website?

  • I can't seem to get a clear answer from people on this, so I'm posing the question to you fine folks.

    If I have a SQL Server 2005 db that powers a website, do I have to buy a CPU license (since there are theoretically millions of "users") or can I just use a 5-seat license (since users aren't being authenticated as unique Windows/SQL Server users)?

    Thanks!

    Regards,

    Eric Schlange

  • you need to get a cpu license, where you will be buying a license for each processor on the machine running the sql server.

    http://www.microsoft.com/sql/howtobuy/sqlserverlicensing.mspx

    and the word doc

    if still in doubt get in touch with a Microsft Licensing partner (Who will probably cost an arm and a leg) but better safe than sorry


    Everything you can imagine is real.

  • eschlange (11/27/2007)


    I can't seem to get a clear answer from people on this, so I'm posing the question to you fine folks.

    If I have a SQL Server 2005 db that powers a website, do I have to buy a CPU license (since there are theoretically millions of "users") or can I just use a 5-seat license (since users aren't being authenticated as unique Windows/SQL Server users)?

    Thanks!

    Regards,

    Eric Schlange

    SQL Server requires that you license all "direct and indirect" users. The example quoted is that of a web site serving content to the outside world.

    You're going to need a processor license (one per processor used in SQL Server).

    ----------------------------------------------------------------------------------
    Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

  • As above, you will need a CPU license for the reasons given. You will need one license per CPU (socket, not core) installed in the server, regardless of whether you intend to use all CPUs with SQL Server or not.



    Scott Duncan

    MARCUS. Why dost thou laugh? It fits not with this hour.
    TITUS. Why, I have not another tear to shed;
    --Titus Andronicus, William Shakespeare


  • Scott Duncan (11/29/2007)


    As above, you will need a CPU license for the reasons given. You will need one license per CPU (socket, not core) installed in the server, regardless of whether you intend to use all CPUs with SQL Server or not.

    Actually - we're apparently both quoting HALF the truth. If you're NOT running a virtual server, you're correct - you need one Processor license per physical processor.

    If on the other hand - you have a virtual server...

    For Workgroup, Standard and enterprise edition, each virtual operating environment running SQL Server 2005 must have a processor license for each processor that the virtual machine accesses. If a copy of SQL is running on a physical operating environment, then processor licenses are required for all of the processors on that physical server. For enterprise edition there is an added option : if all processors in a machine have been licensed, then the customer may run unlimited instances of SQL server 2005 on an unlimited number of virtual operating environments on that same machine.

    ----------------------------------------------------------------------------------
    Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

  • O yeah, I had forgotten about that one.



    Scott Duncan

    MARCUS. Why dost thou laugh? It fits not with this hour.
    TITUS. Why, I have not another tear to shed;
    --Titus Andronicus, William Shakespeare


  • It's a sad truth that it doesn't matter if your users are athenticated or not. Don't go the 5 seat route. If you get caught, you could get majorly fined on what Microsoft says your true traffic is.

    Better just to buckle down and go for the CPU license. It'll be cheaper than perceived per seat licensing and it'll be healthier for your & your organization in the long run. (Less chance of getting called into court if someone from MS catches you).

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

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

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