Post reply

Can someone explain the SQL2000 licensing?

  • March 12, 2002 at 11:40 am

    #57762

    ...in a nutshell?

    I have been tasked to upgrade our existing SQL 7 servers to 2000. We have purchased the Developer's edition to start testing but I would like to load another copy onto a QA box. Are there any connection (number of) restrictions with this version?

    When I'm ready to install on our production box, can I install this version and just buy additional licenses?

  • March 12, 2002 at 12:00 pm

    #425264

    Not sure about this one. Here's the licensing page:

    http://www.microsoft.com/sql/howtobuy/default.asp

    Steve Jones

    steve@dkranch.net

  • March 12, 2002 at 12:22 pm

    #425265

    Thanks Steve... I'll do some research and post an update.

  • March 12, 2002 at 12:33 pm

    #425266

    The answer to your question is it is based on your licensing method.

    quote:

    Processor license. Requires a single license for each CPU in the computer running SQL Server. This license includes unlimited client device access.

    Server/per-seat client access license (CAL). Requires a license for the computer running the Microsoft server product, as well as CALs for each client device. A set number of CALs is included with a server license and the server software.

    If you have a few servers and fewer people hitting most or all then per processor generally works (it is also easier to keep up with as you have unlimited lincense and this is primarily what any website should run).

    Now you second questions is no. You have to license an additional copy of the software:

    quote:

    Server/Per-Seat (CAL) licensing requires a separate Server License (for either SQL Server 2000 Standard or Enterprise Edition) for each server on which the software is installed, and a CAL for each client device.

    Even though you may come out cheaper this is a harder method to keep up with as even though you may have 1 connection from the Web Server to the SQL server you licensing has to be based on the number of connections to the Web Server (you can make it work but they can come after you).

    Generally the rule most poepl I know is for a small company (50) or fewer it may be better to license per seat but growing over that you should role to per processor which you can do but once done you cannot go back.

    Hope this helps.

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

  • March 12, 2002 at 1:02 pm

    #425271

    here's a couple of white papers that seem to clarify.

    Thanks again.

    http://www.microsoft.com/sql/howtobuy/licensingwp.asp

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

Viewing 5 posts - 1 through 4 (of 4 total)

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