Licensing Quick Reference Guide: Microsoft Internal Edition - Do Not Distribute Exter
Licensing Quick Reference Guide: Microsoft Internal Edition - Do Not Distribute Exter
Introduction
Overview
This Quick Reference Guide is for people who need to understand the basics of how Microsoft SQL Server 2008 R2 is licensed and sold. This guide does not supersede or replace any of the legal documentation covering SQL Server use rights. Specific product license terms are defined in the products Software License Terms (in the case of Microsoft Volume Licensing, the Microsoft Volume Licensing agreement under which it was acquired, and/or the Microsoft Volume Licensing Product Use Rights [PUR]). It is not a legal use rights document. Program specifications and business rules are subject to change.
Contents
What is Sold and Who Sells It How it is Sold: Licensing Models for SQL Server 2008 R2 Licensing SQL Server 2008 R2 for Appliances Licensing SQL Server 2008 R2 for Virtualization Scenarios Multiplexing Reassigning Licenses and Moving Running Instances Upgrades, Downgrades, and Step-ups Licensing SQL Server Components Processor, Virtualization, and Memory Support Limits License Grant for Customers with SQL Server Enterprise Licenses with Software Assurance Additional Resources Frequently Asked Questions 1 1 3 5 7 8 8 9 9 10 10 10
2011 Microsoft Corporation. All Rights Reserved. Microsoft, the Microsoft logo, Excel, SQL Server, SharePoint, Windows Server, and the Server Identity Logo are registered trademarks or trademarks of the Microsoft group of companies in the United States and/or other countries. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY. Microsoft provides this material solely for informational and marketing purposes. Customers should refer to their agreements for a full understanding of their rights and obligations under Microsofts Volume Licensing programs. Microsoft software is licensed not sold. The value and benefit gained through use of Microsoft software and services may vary by customer. Customers with questions about differences between this material and the agreements should contact their reseller or Microsoft account manager. Microsoft does not set final prices or payment terms for licenses acquired through resellers. Final prices and payment terms are determined by agreement between the customer and its reseller. Eligibility for Software Assurance benefits varies by offering and region and is subject to change. The Terms and Conditions of your Volume License Agreement and the Terms and Conditions under which any specific Software Assurance benefits are offered will take precedence in the case of any conflict with the information provided here. For eligibility criteria and current benefit program rules, see the Microsoft Product List.
Open Programs
OEM
SQL Server Parallel Data Warehouse (New premium edition SQL Server 2008 R2 Datacenter (Premium edition) SQL Server 2008 R2 Enterprise
(Now available for appliances)
* *
SQL Server 2008 R2 Standard SQL Server 2008 R2 Workgroup SQL Server 2008 R2 Web SQL Server 2008 R2 Developer SQL Server Parallel Data Warehouse for Developers
* The new Parallel Data Warehouse and other specialized SQL Server appliance offerings are available through partnerships with independent hardware vendor (IHV) partners.
Server 1
Server 2
SE
SE
CE
CE
LI
LI
Notes: A Per Processor License is required for each processor installed on each operating system environment (OSE) running SQL Server or any of its components (for example, Analysis Services). For SQL Server running in physical operating system environments (POSEs), you must license all physical processors. Per Processor License costs are the same regardless of number of cores in the processor. The Per Processor model is appropriate when: You cannot or do not want to count users/devices The number of users/devices is high enough that the Per Processor model is more cost-effective than the Server/CAL model SQL Server is being used for external-facing Web sites or applications
Server/CAL Licensing
When licensing SQL Server software under the Server/CAL model, you purchase a Server License for the server and a Client Access License (CAL) for each device (Device CAL) and/or user (User CAL) accessing or using the services or functionality of SQL Server or any of its components (e.g. Reporting Services). A CAL is not software; it is a legal document granting access.
Server License Licenses the server on which SQL Server software or any of its components is running
LI
CE
SE
CAL
Device CAL Licenses a device accessing or using the services or functionality of SQL Server or any of its components
CAL
User CAL Licenses a person accessing or using the services or functionality of SQL Server or any of its components
Notes: SQL Server 2008 R2 CALs (or SQL Server 2008 CALs with SA) are required.
LI
CE
SE
A given user or device only needs one SQL Server CAL to access any number of SQL Server instances in the organization. SQL Server CALs can also be used against any SQL Server regardless of the platform (32 bit, 64 bit, and IA64) or edition (Workgroups, Standard, and Enterprise). Use of hardware and/or software that reduces the number of devices or users that directly access or use the software (multiplexing/pooling) does not reduce the number of CALs required. Separate partitions or blades are considered to be separate servers for licensing purposes. The Server/CAL model is appropriate when: You can count your users/devices The number of users/devices is low enough that the cost is lower than using the Per Processor model You plan to scale out your use of SQL Server by adding new servers over time. (Once you have purchased the necessary CALs, you only need additional Server Licenses for new servers.) Users are accessing many SQL Server databases
SE
LI
CE
LI
CE
SE
LI
CE
SE
LI
The SQL Server software may be installed on any number of non-production devices
Notes: Before you use the software under a license, you must assign that license to one user. That user is the licensed user for that particular license. You may assign other licenses to other users. You may install the software and permit your licensed users to use copies to design, develop, test and demonstrate your programs. You may not use the software in a production environment. For SQL Server 2008 R2 Developer, in addition to the licensed user, any person that has access to your internal network may install and use copies of the software to demonstrate use of your programs with the software. You may reassign a license, but not on a short-term basis (i.e., not within 90 days of the last assignment). If you reassign a license, the user to which you reassign the license becomes the new licensed user for that license.
LI
CE
SE
CE
SE
the software prior to delivery. Each SQL Server Parallel Data Warehouse (PDW) appliance consists of a control rack, plus a minimum of one data rack. Additional data racks can be added for a maximum configuration of up to 40 total compute nodes per appliance. Each control rack includes a control node with two (2) CPUs, with each CPU requiring a SQL Server 2008 R2 Parallel Data Warehouse Per Processor License. Data rack compute nodes also include two (2) CPUs per node and like control nodes, each compute node in the configuration will similarly require two (2) SQL Server 2008 R2 Parallel Data Warehouse Per Processor Licenses. OEM software licenses for Windows Server 2008 are included with the appliance hardware, but customers must acquire licenses through a Microsoft Volume Licensing program for the SQL Server 2008 R2 Parallel Data Warehouse and required Windows HPC Server Pack 2008 R2 Enterprise software components. Notes: SQL Server 2008 R2 Parallel Data Warehouse is licensed under the Per Processor model only. Each data rack contains 8-10 compute nodes, depending on IHV, and all compute nodes in the appliance must be licensed. All Parallel Data Warehouse licenses must be covered by Software Assurance. Parallel Data Warehouse appliances used for development, test and/or demonstration purposes only can be licensed under the Per User model with the SQL Server 2008 R2 Parallel Data Warehouse for Developers edition.
i For more information on licensing SQL Server Parallel Data Warehouse appliances, visit
http://www.microsoft.com/sqlserver/en/us/editions/data-warehouse.aspx
i For more information on the complete portfolio of available appliance offerings for SQL Server, visit
http://www.microsoft.com/sqlserver/en/us/solutions-technologies/appliances.aspx
PDW APPliAnce control rAck + 10-noDe DAtA rAck This example shows the minimum configuration for a 10-node data rack and the SQL Server 2008 R2 Parallel Data Warehouse licenses required.
2 SQL PDW Per Processor Licenses required for each compute node
2 SQL PDW Per Processor Licenses required for each control rack
Control Rack
control noDes Active/PAssive
Data Rack
coMPute noDes DAtABAse servers storAge noDes
SE
LI CE N
SE
LI CE N
LI CE N
SE
SE
LI CE N
MAnAgeMent servers
SE LI LI SE SE LI SE LI SE LI SE LI SE LI SE LI LI CE N SE CE N SE CE N SE CE N SE CE N SE CE N SE CE N SE
SQL
CE
SQL
This configuration would require 22 SQL Server 2008 R2 Parallel Data Warehouse Per Processor Licenses.
LI
SQL
CE
LI
SQL
CE
LI
SQL
CE
LI
CE
LI
SQL
CE
LI
SQL
CE
LI
SQL
CE
CE
SE
LI CE N
SQL
SE
SQL
LI CE N
SQL
SE
If you license all of the physical processors on the server (one license per physical processor), you may run unlimited instances of the SQL Server software in the following number of OSEs (either physical or virtual): Edition SQL Server 2008 R2 Datacenter SQL Server 2008 R2 Enterprise # of OSEs in Which You May Run SQL Server Unlimited Up to 4 per license
In the case of SQL Server 2008 R2 Standard, SQL Server 2008 R2 Workgroup, and SQL Server 2008 R2 Web, if you license all of the physical processors you may run the software in the physical OSE only. In order to run the software in virtual OSEs, you will need to license each virtual processor individually as described below. Licensing a Portion of the Physical Processors If you choose not to license all of the physical processors, you will need to know the number of virtual processors supporting each virtual OSE (data point A) and the number of cores per physical processor/socket (data point B). Typically, each virtual processor is the equivalent of one core:
Virtual machine (VM)
Physical server
With those numbers, you can refer to the table or formula below to determine how many Per Processors Licenses you need for each virtual OSE.
# of Cores per Physical Processor/Socket 1 # of Virtual Processors supporting the virtual OSE 4 3 2 1 4 3 2 1 2 2 2 1 1 4 1 1 1 1 6 1 1 1 1 8 1 1 1 1
# of virtual processors supporting the virtual OSE
Note: For any virtual OSE, you can calculate the number of Per Processor Licenses required for the SQL Server edition that you are licensing by dividing data point A (number of virtual processors supporting the virtual OSE) by data point B (# of cores [if hyperthreading is turned off] or threads [if hyperthreading is turned on] per physical processor). If the result is not a whole number, round up to the next whole number.
Round fractions up to the next whole number
=
# of cores (hyperthreading off) or threads (if hyperthreading on) per physical processor
SQL Server 2008 R2 CALs are required for any user or device accessing the SQL Server functionality or data, regardless of whether SQL Server or any of its components are running in the physical or virtual OSE.
i For more information on licensing SQL Server for virtual environments, visit
http://www.microsoft.com/licensing/about-licensing/virtualization.aspx
Multiplexing
A SQL Server CAL and Windows Server CAL are required for each distinct device or user that is connected to the multiplexing or pooling software or hardware front end:
CAL
With multiplexing
CAL
Without multiplexing
CAL
CAL
The number of tiers of hardware or software between the SQL Server and the user or devices that ultimately use its data, services, or functionality does not affect the number of CALs required:
CAL
With multiplexing
CAL
SharePoint portal
CAL
Without multiplexing
CAL
Manual transfer of data from employee to employee does not require a CAL for the receiving employee. For example, if an employee sends a Microsoft Office Excel version of a report to another employee, the receiving employee does not require a CAL (as long as the report does not access a server running SQL Server in some way):
Manual forwarding of reports
CAL
With multiplexing
Without multiplexing
Manual forwarding of reports
CAL
i For more information on how multiplexing affects the licensing of SQL Server licensed under the server/CAL model,
download the Volume Licensing Brief at http://download.microsoft.com/download/8/7/3/8733d036-92b0-4cb8-8912-3b6ab966b8b2/multiplexing.doc
Moving Running Instances of SQL Server 2008 R2 Enterprise Under Server/CAL Model
You may move licensed instances as needed across the server farm as long as the number of servers on which you are running instances of the software does not exceed the number of licenses assigned to the server farm.
i For more information on SQL Server license mobility, download the Volume Licensing Brief at
http://download.microsoft.com/download/6/9/5/695BA00D-C790-4C90-813A-F10539D97991/Application_Server_ License_Mobility_VL_Brief_Nov_2008.docx
Down Edition Rights* (New with SQL Server 2008 R2) Edition Step-Up
Move from lower edition (e.g. Standard) to higher edition (e.g. Enterprise)
Lower edition must be covered by Software Assurance (SA) You acquire the SA Step-Up SKU offered through certain Volume Licensing programs Step-ups available from Workgroup to Standard, Standard to Enterprise, and Enterprise to Datacenter
*When utilizing version downgrade or down edition rights, the product use rights for the originally licensed version and edition still apply. Downgrade and/or down edition rights may not apply when licensing SQL Server for appliances.
Edition Step-up
CE
CE
LI
LI
Notes: With the introduction of SQL Server 2008 R2, the processor, virtualization and memory limits for the SQL Server Standard and Enterprise editions have been recalibrated from the previous 2008 version offerings. The following is considered a single processor for purposes of this table: A single-core, hyper-threaded processor with two logical CPUs per socket A dual-core processor with two logical CPUs A quad-core processor with four logical CPUs
i For a detailed comparison of the key capability differences between SQL Server editions, visit
http://www.microsoft.com/sqlserver/en/us/product-info/compare.aspx
LI
CE
License Grant for Customers with SQL Server Enterprise Licenses with Software Assurance
If you have active Software Assurance coverage for SQL Server Enterprise, Microsoft is granting you the following additional use rights until the release of the SQL Server version that follows SQL Server 2008 R2: If licensed under Server/CAL model for SQL Server Enterprise with Software Assurance You may run any number of instances of the SQL Server 2008 R2 Enterprise software in one physical OSE and any number of virtual OSEs on the licensed server If licensed for all physical processors under Per Processor model for SQL Server Enterprise with Software Assurance You may run any number of instances of the SQL Server 2008 R2 Enterprise software in one physical OSE and any number of virtual OSEs on the licensed server
Note: Details on product use rights and migration paths for the release of the SQL Server version that follows SQL Server 2008 R2 will be made available closer to the release date of that version.
Additional Resources
For more information about licensing SQL Server 2008 R2, including what is new with version 2008 R2, please visit these websites: For detailed SQL Server product licensing information including new version features, edition comparisons, benchmarks, competitive comparisons and more, visit: http://www.microsoft.com/sqlserver/en/us/default.aspx For SQL Server Product Use Rights and other information on general Volume Licensing topics, visit: http://www.microsoft.com/licensing/about-licensing/product-licensing.aspx For a list of dependent licenses required for SQL Server under the terms of Volume Licensing programs, download the Software Dependency Guide at: http://download.microsoft.com/download/1/5/C/15CCF7C4-403D-4893-988B58FD7B8BC87D/Software_Dependency_Guide.docx Volume Licensing Briefs provide in-depth knowledge of key licensing topics, including Application Server License Mobility, Product Downgrade Rights, Step-Up Licensing, Multiplexing and more. To view the complete list of available licensing briefs, visit: http://www.microsoft.com/licensing/about-licensing/volume-licensing-briefs.aspx To download a current copy of this SQL Server 20008 R2 Licensing Quick Reference Guide and get more information on how to acquire SQL Server software licenses, visit: http://www.microsoft.com/sqlserver/en/us/get-sql-server/howto-buy.aspx
10
What is the scenario for grandfathering unlimited virtualization rights for SQL Server 2008 Enterprise? SQL Server 2008 Enterprise licenses with Software Assurance acquired prior to the release of SQL Server 2008 R2 will be granted the right to run in unlimited VMs. This right is remains in effect as long as Software Assurance coverage remains active and until the SQL Server version that follows SQL Server 2008 R2 is generally available. If you acquire new licenses (on a new or existing contract), you will also be granted similar rights to run unlimited VMs if you acquire Software Assurance. I acquired SQL Server 2008 R2 Enterprise License with Software Assurance and want to create unlimited VMs using SQL Server 2008 R2 Standard. Can I do this? Yes. The new down edition rights announced with SQL Server 2008 R2 allow you to deploy the Standard edition in place of Enterprise edition, and as long you remain active on your Enterprise Software Assurance, the right to run in unlimited VMs will continue until the next version of SQL Server after SQL Server 2008 R2 is generally available. I acquired two Datacenter licenses and installed those on a server with four processors. Can I create unlimited VMs? You need to license all physical processors in order to run instances of SQL Server 2008 R2 Datacenter in an unlimited number of virtual OSEs. In this case, you will need four Datacenter licenses. What are the licensing requirements for PowerPivot? PowerPivot for Microsoft Excel 2010 is available for download as a free data-analysis add-in. To enable sharing and collaboration on PowerPivot for Excel applications and models with Microsoft SharePoint 2010, you must install SQL Server 2008 R2 as part of a SharePoint farm. The server component in this scenario is PowerPivot for SharePoint and is available as a SharePoint Enterprise edition feature that requires both SharePoint Standard and SharePoint Enterprise CALs, in addition to a SharePoint 2010 server license. Support for the PowerPivot IT operation dashboard is a premium feature offered with the SQL Server 2008 R2 Enterprise and Data Center editions only and the standard SQL Server licensing terms and policies apply. Can I have a standalone PowerPivot for Excel installation without SQL Server 2008 R2? Yes. The PowerPivot client component is a standalone Excel 2010 add-in that can query any data source, including SQL Server. What is SQL Server 2008 R2 Parallel Data Warehouse? The SQL Server 2008 R2 Parallel Data Warehouse is a highly scalable data warehouse appliance that delivers performance at low cost through massively parallel processing (MPP). SQL Server 2008 R2 Parallel Data Warehouse is the integration of DATAllegros MPP Data Warehouse software and methodology with the SQL Server platform and provides scalability to 100s of terabytes of data at low cost. What is the Microsoft Critical Advantage Program (MCAP)? Microsofts Critical Advantage Program combines industry-leading technologies with enterprise class service and support to deliver an elastic, failure resistant, scalable and secure platform for mission critical applications. The key components of this program include appliances to support tier 1 workloads, such as the Microsoft SQL Server 2008 R2 Parallel Data Warehouse, along with enhanced services and support offerings. What is an appliance? A server appliance is a computer system consisting of hardware and software, which is pre-configured and pre-tested by the manufacturer to perform a specified workload and delivered to the customer as a single unit. Server appliances are designed to be easy to operate, be useable in minutes, and provide strong reliability and security for the workloads they run (e.g., data warehouse, business intelligence, email, transaction processing). How is SQL Server licensed for appliances? SQL Server licensing requirements will depend on the licensing model deployed, the actual hardware architecture of the appliance (the number of CPUs for example) and/or the specific workload for which the appliance is optimized, such as data warehousing appliances optimized for the SQL Server 2008 R2 Parallel Data Warehouse edition, or self-service business intelligence appliances that are optimized for PowerPivot and the SQL Server 2008 R2 and SharePoint 2010 Enterprise editions. While appliances are pre-installed and configured with Microsoft software prior to customer delivery, actual licenses for the SQL Server products included as part of an appliance offering must be acquired separately under a Microsoft Volume SQL Server LicenSing Quick reference guide 11
License agreement, and additional terms and conditions may apply. How can customers buy SQL Server 2008 R2 Parallel Data Warehouse? Parallel Data Warehouse appliances are being sold through preferred hardware partners, who will preinstall and configure the software prior to delivery. Customers must purchase licenses for the required SQL Server 2008 R2 Parallel Data Warehouse and HPC Pack 2008 R2 Enterprise software and required support components under a Microsoft Volume Licensing agreement, through a Microsoft Enterprise Software Advisor or Large Account Reseller. What are the SQL Server 2008 R2 Parallel Data Warehouse software license requirements? Each production-use Parallel Data Warehouse appliance consists of a control rack, plus a minimum of one data rack with 8-10 compute nodes, depending on hardware vendor. Additional data racks can be added, for a maximum configuration of up to 40 total compute nodes per appliance. Each compute node requires two SQL Server 2008 R2 Parallel Data Warehouse processor licenses, and each control rack additionally requires two SQL Server 2008 R2 Parallel Data Warehouse processor licenses, for a total of 82 Parallel Data Warehouse processor licenses needed for a fully configured appliance. Applicable HPC Pack 2008 R2 Enterprise server licenses are also required. Can I re-assign my current Microsoft server licenses for use with an appliance offering? Yes. As long as it is not within 90 days of any prior server assignment, available HPC Pack 2008 R2 Enterprise server licenses may be reassigned to a SQL Server Parallel Data Warehouse appliance as needed. Likewise, existing SQL Server 2008 R2 Enterprise and/or SharePoint 2010 licenses can similarly be re-assigned to appliance offerings that are optimized for these products. Usage is subject to the agreement terms under which these reassigned licenses were initially acquired. What are the support and maintenance requirements for Parallel Data Warehouse? All appliances offered under the MCAP program, including Parallel Data Warehouse, are licensed with Software Assurance plus Premier support (SA+Premier) as an add-on to a Premier Standard or higher service agreement. Customers are encouraged to upgrade their Premier coverage to Premier Mission Critical, providing for the highest level of support with additional benefits that include rapid response and escalation of Severity 1/A incidents and a dedicated Microsoft Support Engineer. Can Parallel Data Warehouse be added to an existing Enterprise Agreement (EA), including the Enrollment for Application Platform (EAP)? Yes. SQL Server 2008 R2 Parallel Data Warehouse software is offered as an Additional Product that can be included on a new or existing EA or EAP agreement. Parallel Data Warehouse software can also be purchased through the Select program, or by subscription under an Enterprise Subscription Agreement. How is SQL Server 2008 R2 Parallel Data Warehouse being licensed for non-production use? Single-rack appliances designed for non-production use will be available from all hardware partners. While limited in size to only two total compute nodes, Parallel Data Warehouse Development/Test appliances include the full software functionality of a production appliance, but are licensed for development, test and demonstration use only. Each user accessing a Parallel Data Warehouse Development/Test appliance must be assigned a SQL Server 2008 R2 Parallel Data Warehouse for Developers license, which can be used to access one or more Development/Test appliances. Similar to appliances for production use, server licenses for Windows Server 2008 and HPC Pack 2008 R2 are additionally required. Can SQL Server 2008 R2 Parallel Data Warehouse for Developer licenses be used against full data rack appliance configurations, typically purchased for production use? As long as the appliance is only used for development, test and/or demonstration purposes and each user accessing the appliance is licensed accordingly there is no restriction to licensing this way. Can a Parallel Data Warehouse Development/Test appliance be licensed for production use? No, Parallel Data Warehouse Development/Test appliances are only supported for development, test and/or demonstration purposes.
12