RE: licensing in SQL 2k

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Ashish Ruparel [MSFT] (v-ashrup_at_online.microsoft.com)
Date: 04/22/04 

Date: Thu, 22 Apr 2004 22:13:08 GMT

Hi Ray,

Below is a Question that I found in the FAQ section of SQL's Licensing.

Q. How do I license SQL Server 2000?
   
A. In general, there are three options for licensing SQL Server in a
production environment:

Processor license. Requires a single license for each CPU in the operating
system instance running SQL Server. If you have made a processor
inaccessible to all operating system copies on which the SQL Server
software is set up to run, you do not need a software license for that
processor. This license does not require any device or user client access
licenses (CALs).

Server plus device CALs. Requires a license for the device or user running
SQL Server, as well as a CAL for each client device.

Server plus user CALs. Requires a license for the computer running SQL
Server, as well as a CAL for each user.

Per Processor License - If you buy a per processor license, you DO NOT
require CALS. It accomodates all the clients that get connected to the SQL
Server. But, you need to buy a software license for Each of the Processor.

You need to buy Separate CALs for each client that gets connected
simultaneously to your SQL Server. CALs are available in two options, Per
Device CALs and Per User CALs.

Per Device CALs - Use this CALs option, if one device would be used by
multiple users at different times. For Eg. People working in different
shifts share the same computer to get connected to the SQL server. So in
this case it would be economical to go for the Per Device CALs.

Alternatively,
Per User CALs - Use this CALs option, if the same user would be connecting
to the SQL Server simultaneously from different Devices. For Eg. Developers
who connect to the SQL server from the development machine and might also
connect to the SQL server from the Test Machine. In this case it would be
economical to go for the Per User CALs

You can also visit the following url to get answers to an exhaustive list
of FAQs
http://www.microsoft.com/sql/howtobuy/faq.asp

HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

Relevant Pages

  • Re: SQL Licensing--CALs
    ... The vendor is saying I do not need CALs because the application ... The SQL Server licensing is quite clear ... My boss doesn't want to get per-processor license. ... connections thru SQL software or IIS software, ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL Server License Control and Management
    ... license, and than match it to my HR system. ... If user is an employee I ... Like I said, CALs ... David Portas, SQL Server MVP ...
    (comp.databases.ms-sqlserver)
  • Re: SQL Licensing
    ... You need 25 CALs, or if you are running Standard Edition, you might as well ... It's the end users/devices that count for the license, ... SQL Server MVP ...
    (microsoft.public.sqlserver.server)
  • Re: SharePoint (not Portal) Licensing
    ... Windows Svr Cals for each device or user accessing the server. ... customer is running Sharepoint Servcies with SQL server, ... also need SQL Svr license and each device or user would also need a SQL CAL. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Are multiple-instances on a single cluster supported with SQL Server 2005 Standard Edition?
    ... If you have a per-proc license, you can run as many instances as your system ... can hold on the cluster. ... Personally, I would go with Standard Edition for a two-node, four-proc SQL ... Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.clustering)