Source: http://docplayer.net/1600393-Licensing-guide-microsoft-internal-edition-do-not-distibute-externally-version-1-0-6-17-09.html
Timestamp: 2017-02-28 16:58:44
Document Index: 441757235

Matched Legal Cases: ['art 1', 'art 2', 'art 1', 'art 1', 'art 1', 'art 1', 'art 1', 'art 1', 'art 1', 'art 1', 'art 1', 'art 1', 'art 1', 'art 1', 'art 1', 'art 1', 'art 1', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2']

Licensing Guide. Microsoft Internal Edition - Do Not Distibute Externally. Version 1.0 6/17/09 - PDF
Download "Licensing Guide. Microsoft Internal Edition - Do Not Distibute Externally. Version 1.0 6/17/09"
1 Licensing Guide Microsoft Internal Edition - Do Not Distibute Externally Version 1.0 6/17/092 2009 Microsoft Corporation. All Rights Reserved. Microsoft, the Microsoft logo, Active Directory, BizTalk, Excel, Forefront, Hyper-V, Microsoft Dynamics, SQL Server, SharePoint, Windows, Windows Server, Windows Vista, and the Server Identity Logo are registered trademarks or trademarks of the Microsoft group of companies in the United States and/or other countries. All other trademarks are property of their respective owners. The example companies, organizations, products, domain names, addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, address, logo, person, places, or events is intended or should be inferred. 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 Microsoft s 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. The contents of this guide are subject to change. Please go to aspx for the most current version of this guide. i3 Introduction Overview This guide is for Microsoft customers who need to understand how Microsoft SQL Server is licensed and sold. In addition to information about SQL Server releases and sales channels, you will find step-by-step instructions and examples for determining when a server or client needs to be licensed and how to calculate the required licenses. Among the scenarios covered are: Running SQL Server in physical and/or virtual operating system environments High availability/failover Server farms Multiplexing Multi-instancing More... Appropriate Use This guide is intended to be used to help Microsoft customers gain a basic understanding of the licensing models and rules for SQL Server and to help you determine the correct license requirements for a given scenario. Most scenarios are covered here. If you cannot find the information you need for a specific scenario in this guide, contact your Microsoft reseller or account manager. 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 product s Software License Terms, the Microsoft Volume Licensing agreement under which it was acquired, and/or the Microsoft Volume Licensing Product Use Rights (PUR). It is not for external distribution, nor is it a legal use rights document. Program specifications and business rules are subject to change. This will be updated as needed. For the latest version, please visit Contents Chapter 1: What is Sold: SQL Server Releases 1 Chapter 2: Who Sells It: Sales Channels for SQL Server 6 Chapter 3: How Licenses are Counted: Licensing Models for SQL Server 11 Chapter 4: How to Count Licenses in Advanced Scenarios Part 1: Virtualization and License Mobility 21 Chapter 5: How to Count Licenses in Advanced Scenarios Part 2: High Availability, Multiplexing, and Components 35 Chapter 6: Other Microsoft Products that Run on SQL Server 48 Chapter 7: Upgrades, Downgrades, and Step-ups 54 Chapter 8: Software for Evaluation, Development, Training, and Demos 57 Chapter 9: Media Fulfillment 59 Chapter 10: Pricing and Additional Resources 60 Introduction i4 Chapter 1: What is Sold: SQL Server Releases In this Chapter SQL Server Versions and Editions 1 Hardware Platforms Supported 3 Multi-Language Support 3 Restrictions on Deployment 4 Key Terms Introduced Edition: The level of the product (e.g. Enterprise or Standard ) Platform: The operating system environment on which applications run (e.g. x86 [32-bit] or x64 [64-bit]) Version: The release of the product (e.g. SQL Server 2005 or SQL Server 2008) SQL Server Versions and Editions The table below provides a summary of the versions and editions for Microsoft SQL Server 2008, SQL Server 2005, and SQL Server Note: The information and examples used in this guide generally apply to SQL Server Licensing rules for prior versions are the same except where noted. Table 1.1: SQL Server Versions and Editions Editions Platforms Supported x86 (32-bit) x64 (64-bit) IA64 (64-bit Itanium) SQL Server 2008 Enterprise SQL Server 2005 Enterprise SQL Server Enterprise Target Scenarios for SQL Server 2008 Editions Enterprise workloads that need redundancy and built-in Business Intelligence Enterprise virtualization Server farm with license mobility SQL Server 2008 Standard Shared data scenarios in departments and small to large businesses SQL Server 2005 Standard Departmental SQL Server 2000 Standard Essential Business Server customers SQL Server 2008 Developer Full featured edition for development and testing only SQL Server 2005 Developer SQL Server 2000 Developer SQL Server 2008 Workgroup Remote/branch offices that need local instances of company data SQL Server 2005 Workgroup Small scale Chapter 1: What is Sold: SQL Server Releases 15 Editions Platforms Supported x86 (32-bit) x64 (64-bit) IA64 (64-bit Itanium) Target Scenarios for SQL Server 2008 Editions SQL Server 2008 Compact 3.5 Developing desktop and mobile applications SQL Server 2005 Compact SQL Server 2005 CE Client embedded SQL Server 2008 Web Web application hosting SQL Server 2008 Express SQL Server 2008 Express with Tools SQL Server 2008 Express with Advanced Services SQL Server 2008 Standard Edition for Small Business 2 SQL Server 2008 Enterprise Evaluation SQL Server 2000 Personal 1 SQL Server 2000 is no longer available for purchase. Entry-level Learning Core database engine only ISV distribution Free Same as Express, but with SQL Server Management Studio Basic Same as Express with Tools, but with SQL Server Reporting Services and Text-based Search Small businesses with fewer than 75 users 180-day trial Free 2 Any number of instances of the server software may be run in one physical or virtual operating system environment (OSE) on the licensed server at a time. The OSE in which instances of the server software run must be joined to a domain that has Microsoft Active Directory configured to have a single server in the domain that contains all the flexible single master operations (FSMO) roles and is the root of the Active Directory forest, no trust relationships with any other domains, no child domains, and no more than 75 total users/devices. i For more information, visit Chapter 1: What is Sold: SQL Server Releases 26 Hardware Platforms Supported SQL Server products may be used on any hardware platform on which the software runs. Diagram 1.1: SQL Server Licenses are Platform Independent SQL Server licenses and installation media allow you to install any platform of the licensed edition. x86 Install Files x64 Install Files IA64 Install Files OR OR x86 x64 IA64 Multi-Language Support SQL Server 2008 is available in the following languages: English Chinese Simplified Chinese Traditional French German Italian Japanese Korean Portuguese (Brazilian) Russian Spanish Chapter 1: What is Sold: SQL Server Releases 37 Diagram 1.2: SQL Server All Language SKUs SQL Server All Language SKUs through Microsoft Volume Licensing permit you choose which language you deploy: Volume Licensing All Language SKU English OR Spanish OR German! Rule 1.1: Changing Languages If you are licensed for a specific language through Volume Licensing, you may change to a different language provided that the license price for the new language is less than or equal to the license price for the current language. Restrictions on Deployment Depending upon the edition of SQL Server, certain limits may apply to how the product may be deployed. Below is an overview of the primary limits. Note: This is a summary only. See Chapter 2 for more information about where to find the applicable terms and conditions. Additionally, limits on memory are affected by the specific configuration. Table 1.2: Processor, Memory, and Database Size Limits by SQL Server 2008 Edition Enterprise Standard Workgroup Web Developer Express Compact # of Processors 1 OS Maximum CPU OS Maximum 1 OS Maximum Memory OS Maximum OS Maximum 4 GB (64-bit)/ OS Maximum (32-bit) OS Maximum OS Maximum 1 GB ~1.5 MB DB Size Unlimited Unlimited Unlimited Unlimited Unlimited 4 GB 4 GB 1 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 Chapter 1: What is Sold: SQL Server Releases 48 Table 1.3: Some Additional Limitations for SQL Server Developer and Web Editions Permitted Not Permitted Web Developer Internalfacing Externalfacing Development, testing, and internal demos Not applicable Web apps, sites, and services Production environments Web apps, sites, and services Line of Business apps (e.g. CRM, HR) Line of Business apps Chapter 1: What is Sold: SQL Server Releases 59 Chapter 2: Who Sells It: Sales Channels for SQL Server In this Chapter Overview of Sales Channels for SQL Server 6 Volume Licensing Programs for End Customer Organizations 7 Volume Licensing SKU Types 7 Volume Licensing Program Types 9 Perpetual and Temporary Licenses 9 Overview of Volume Licensing Programs for End Customer Organizations 10 Key Terms Introduced Comprehensive licensing: Programs through which customers pay for license coverage on an annual basis based on a counting mechanism Full Packaged Product (FPP): Boxed product sold through the retail channel License (L): SKU type that provides customer with the right to use the product License & Software Assurance Pack (L/SA): SKU type that includes both the License and Software Assurance for the product PUR: Product Use Rights are the legal terms and conditions for products licensed through the Volume Licensing channel Software Assurance (SA): Program offering that provides automatic access to new technology and productivity benefits, support, tools, and training to help deploy and use software efficiently Software License Terms: Legal terms governing use of single software titles acquired by an individual through the retail or OEM channels. Stock Keeping Unit (SKU): Part number used to order a license Transactional licensing: Programs through which customers acquire licenses and/or Software Assurance on an as-need basis Volume Licensing: Purchasing programs that provide discounts to organizations acquiring multiple licenses Overview of Sales Channels for SQL Server Microsoft sells Microsoft SQL Server licenses through channels designed to meet the unique needs of customers. The channel the licenses are sold through determines which document(s) details the use rights for the licensed products. Table 3.1: Overview of SQL Server Sales Channels Who Sells it to End Customers Program Who Can Participate Online retailers Microsoft (direct) - Enterprise Software Advisors (ESAs) Resellers (indirect) - Large Account Resellers (LARs), Authorized Education Resellers (AERs) Original Equipment Manufacturers (OEM) Full Packaged Product (FPP) Volume Licensing for End Customer Organizations OEM Royalty, OEM Embedded End customers/consumers needing a single copy of SQL Server Qualifying customer organizations 2 OEMs selling SQL Server with hardware Product Use Rights Detailed In Retail version of Software License Terms 1 Microsoft Volume Licensing Product Use Rights (PUR) 3 OEM version of Software License Terms Independent Software Vendors (ISVs) ISV Royalty Licensing Program (ISVR) ISVs integrating SQL Server into software business applications sold to end customers ISV Royalty Agreement 3 Application Service Providers (ASPs) Services Provider License Agreement (SPLA) Service providers licensing SQL Server on a monthly basis to provide services and hosted applications to their end customers Service Provider User Rights (SPUR) 3 1 Channel partner agreement may override the Software License Terms in some cases 2 Qualifications vary by program, organization type, and purchase quantity 3 Important product use rights information is also included the Microsoft Volume Licensing Product List and the customer s licensing agreement Chapter 2: Who Sells It: Sales Channels for SQL Server 610 Volume Licensing Programs for End Customer Organizations Microsoft offers Volume Licensing programs designed to meet the purchasing and software asset management needs for end customer organizations of various sizes, with various needs, and across various industries. Volume Licensing SKU Types SKUs (Stock Keeping Units) are the part numbers on the Microsoft Volume Licensing price lists that are used to order a particular item. There are four licensing SKU types available to customers for SQL Server products through Microsoft Volume Licensing programs. Diagram 2.1: Volume Licensing SKU Types License (L) Part Number Item Name Product Type SQL Svr Enterprise Edtn 2008 All Lng MVL Standard Software Assurance (SA) Part Number Item Name Product Type SQL Svr Enterprise Edtn All Lng SA MVL Software Assurance License and Software Assurance Pack (L/SA) Part Number Item Name Product Type SQL Svr Enterprise Edtn All Lng Lic/SA Pack MVL License/Software Assurance Pack SA Step-Up Part Number Item Name Product Type SQL Svr Enterprise Edtn All Lng SA Step Up MVL SQL Svr Std SA Step Up Use to license a specific version and edition of the software Also referred to as Standard SKU Use only to renew/extend SA coverage or to enroll qualifying OEM or FPP licenses in SA within 90 day of license purchase In addition to other benefits, permits you to upgrade to new releases of the software during the SA term Use to acquire both a license and SA coverage for the license Use to migrate customers with SA from a lower edition to a higher edition of the software Chapter 2: Who Sells It: Sales Channels for SQL Server 711 Software Assurance Overview The table below shows the Software Assurance benefits applicable to SQL Server that are available to commercial and government Volume Licensing customers. Table 3.2 Software Assurance Benefits that Are Applicable to SQL Server Open License Select License and Select Plus Open Value Noncompany-wide Open Value Company-wide and Subscription Select License with SAM, Select Plus with SAM, Enterprise Agreement, Enterprise Subscription Agreement New Version Rights Spread Payments E-Learning 24x7 Problem Resolution Support Cold Backups for Disaster Recovery TechNet Subscription Extended Hotfix Support Options At the End of the SA Term When you wants SA coverage on a new license, the L/SA SKU is used. If you choose to extend the SA coverage when it expires, you purchase just the SA SKU. If you do not extend your SA coverage, you can continue to use the most current version of the software (or a downgrade version), but will not be entitled to further upgrades. To upgrade in the future, you would need to acquire a new License (L) or L/SA. Note: The term of the SA coverage depends upon the licensing agreement under which it was acquired and the timing of the purchase. Example 2.1: Customer with L/SA for SQL Server 2005 Standard License term SA term Customer buys perpetual license with SA using SQL Server 2005 Standard L/SA SKU Customer receives upgrade to SQL Server 2008 Standard at no additional cost through SA New Version Rights benefit SA coverage expires Customer may: 1. Extend coverage by purchasing SA SKU, or 2. Continue using SQL Server 2008 Standard (or a downgrade version) without rights to future upgrades (or purchase a new L or L/SA to upgrade in the future.) Chapter 2: Who Sells It: Sales Channels for SQL Server 812 Enrolling OEM or FPP Licenses in Software Assurance If you purchase SQL Server though the retail FPP or OEM channels, you have 90 days to enroll the license in SA. To do so, you purchase the SA SKU through a Volume Licensing program. Volume Licensing Program Types Microsoft Volume Licensing programs can be classified into two general categories: Transactional and Comprehensive (also referred to as subscription or annuity ). Table 3.3: Transactional vs. Comprehensive Volume Licensing Programs Transactional You acquire licenses and/or Software Assurance as needed Comprehensive Depending on the Volume Licensing program, you make an annual payment based on counting desktops, installed copies, or Full-time Equivalent Employees (FTE) Perpetual and Temporary Licenses Depending upon the Volume Licensing program, licenses are offered as perpetual or temporary (non-perpetual). Perpetual licenses never expire and permit the owner to use the licensed software for an unlimited period of time. Non-perpetual licenses permit the user to use the licensed software for a specified period of time. Temporary licenses are only available through certain comprehensive licensing programs. Diagram 2.2: License Term for Perpertual vs. Non-perpetual Licenses Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Perpetual license Temporary license with one-year term Chapter 2: Who Sells It: Sales Channels for SQL Server 913 Overview of Volume Licensing Programs for End Customer Organizations The following table provides an overview of the Volume Licensing programs available to end customer organizations. Table 3.4: Microsoft Volume Licensing Programs for End Customers (T) = Temporary licenses offered Customer Organization Size Small to Midsize Midsize to Large Customer Industry Commercial Academic Open License Transactional Open License for Academic Program Type Open Value Comprehensive Open Value Subscription (T) Government Open License for Government Open Value for Government Nonprofit Commercial Academic Government Open License for Charities Select License Select Plus Note: Program availability may vary by geographical region. Select License for Academic Select Plus for Academic Enterprise Agreement for Government Select License for Government Select Plus for Government Enterprise Agreement Enterprise Subscription Agreement (T) Campus and School Agreement (T) Enterprise Subscription Agreement for Government (T) i For more information, go to Chapter 2: Who Sells It: Sales Channels for SQL Server 1014 Chapter 3: How Licenses are Counted: Licensing Models for SQL Server In this Chapter Overview 11 Anatomy of a Server 11 Server/ Licensing 12 Multi-core Processors 16 Choosing the Best Model 16 Assessing Your Needs 20 Key Terms Introduced Client Access License (): License granting a device or user the right to access or use the services or functionality of the server software Core: Processing execution unit on a processor Device : Licenses a device accessing or using the services or functionality of the server software Multi-core processor: A processor chip that consists of multiple processing execution units or cores Per Processor: Licensing model based on the number of processors; permits an unlimited number of users or devices to access or use the services or functionality of the server software Processor: A complete computation engine that is fabricated on a single chip and performs the work of the computer. (Also referred to as a microprocessor or CPU (central processing unit) Physical operating system environment (POSE): Computing environment on the physical hardware in which the operating system and applications run Server/ licensing: Licensing model where licenses are acquired for both the server on which the server software is run and the users and/or devices accessing or using the services or functionality of the server software Server license: Licenses the server on which SQL Server software or any of its components is running User : Licenses a user accessing or using the services or functionality of the server software Virtual machine (VM): A software implementation of a computer that executes programs like a real computer Virtual operating system environment (VOSE): Virtual environment in which the operating system is emulated and applications (such as SQL Server) run Virtualization: Running software in a virtual operating environment Overview When licensing Microsoft SQL Server through your Microsoft Volume Licensing agreement, you may choose between two main licensing models: Server/Client Access License () and Per Processor. This chapter includes guidance about the different models and general guidelines as to which is recommended for certain scenarios. Anatomy of a Server The diagram below shows how the key components of a physical server (also referred to as the physical machine ) and a virtual machine (VM) on which SQL Server is running are represented in the various diagrams and examples that follow. Chapter 3: How Licenses are Counted: Licensing Models for SQL Server 1115 Diagram 3.1: Physical Server and Virtual Machine Running SQL Server Physical Server with SQL Server Running in the POSE Virtual Machine (VM) with SQL Server Running in the VOSE (VM runs on a physical server) Running instance of SQL Server Operating system Physical OS Environment (POSE) Running instance of SQL Server Operating system Virtual processor Virtual OS Environment (VOSE) Physical processor Physical server Server/ Licensing When licensing SQL Server under the Server/ model, you purchase a Server license for the server and Client Access Licenses (s) for each device (Device s) and/or users (User s) accessing or using the services or functionality of SQL Server. A is not software; it is a legal document granting access. Note: Separate partitions or blades are considered to be separate servers for licensing purposes. Diagram 3.2: Server License and s Server license Licenses the server on which SQL Server software or any of its components is running Device Licenses a device accessing or using the services or functionality of SQL Server or any of its components User Licenses a person accessing or using the services or functionality of SQL Server or any of its components Chapter 3: How Licenses are Counted: Licensing Models for SQL Server 1216 ! Rules 3.1 Counting s A given user or device only needs one SQL Server to access any number of SQL Server instances in your organization. SQL Server Workgroup and SQL Server Standard for Small Business editions have their own s that can only be used with those respective editions. SQL Server s can be used with any edition of SQL Server, including SQL Server Workgroup and SQL Server Standard for Small Business editions. Windows Small Business Server (SBS) 2008 Suite for Premium Users or Devices may be used instead of SQL Server 2008 s to access instances of the server software within an SBS domain. Servers running SQL Server instances that connect to other servers running SQL Server instances require Server licenses, but do not require SQL Server s Manual data-transfer to/from SQL Server does not require s. For instance, if User A sends data to User B, who in turn enters data into SQL Server, User A does not need a. SQL Server s can also be used against any SQL Server regardless of the platform (32 bit, 64 bit, and IA64). If enrolled in Software Assurance (SA) or Enterprise Agreement (EA), you can switch from Device s to User s, or from User s to Device s, upon renewal of SA or EA. Users or Devices accessing SQL Server components (e.g. Reporting Services) require s 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 s required. See Multiplexing section in Chapter 5 for more information. If a user or device is accessing an application that connects to SQL Server (directly or indirectly), a is required even the application and SQL Server are running on different physical hardware systems. See Multiplexing section in Chapter 5 for more information. Diagram 3.3: Counting Server/ Licenses for a Single Physical Server Under the Server/ model, you must purchase and assign one SQL Server license to each server: Next, s are required for either the devices or the users that connect to or use the SQL Server data. If s are purchased for a device, any number of users can use that device to connect to and use the SQL Server data: Chapter 3: How Licenses are Counted: Licensing Models for SQL Server 1317 Diagram 3.4: You May Use a Combination of User s and Device s Sales Force (User s) Call Center (Device s) Vendors (User s) Diagram 3.5: SQL Server s Permit Access to Any Licensed Server SQL Server s permit access to any licensed server within your organization. Additional s are not required for additional servers: Chapter 3: How Licenses are Counted: Licensing Models for SQL Server 1418 Per Processor Licensing Microsoft offers a Per Processor licensing model to help alleviate complexity. When licensing SQL Server under the Per Processor model, you do not need to purchase additional s; it includes access for an unlimited number of users or devices to connect from either inside or outside the firewall. Processor licenses for SQL Server 2008 are available for Enterprise, Standard, Web, and Workgroup editions.! Rules 3.2: Per Processor Licensing A 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 each physical processor. i For more information about how to calculate the required number of Processor licenses for SQL Server running on a virtual machine (VM), refer to Chapter 4. Example 3.1: Counting Processor Licenses for Two Physical Servers Server 1 below has one processor and Server 2 has two processors, therefore three Processor licenses are required: Server 1 Server 2 With those three Processor licenses, any number of devices and users may connect to and use the SQL Server data on the servers. s are not required: Server 1 Server 2 Chapter 3: How Licenses are Counted: Licensing Models for SQL Server 1519 Multi-core Processors Multi-core processors, which consist of multiple processing execution units or cores on one chip, are seen as a promising way to boost computing power. For Processor licenses, Microsoft charges by the processor, not by the core. Diagram 3.6: Multi-core Processors Each of these physical processors would require a single Processor license for SQL Server: core Single core processor Dual core processor Quad core processor Eight core processor Choosing the Best Model Use this information as a guide to finding the most appropriate licensing model for a given scenario. Chapter 3: How Licenses are Counted: Licensing Models for SQL Server 1620 ? Decision Tree 3.1: General Guidance on Choosing a Licensing Model for a Single Project Will SQL be deployed in a Web setting with access from beyond the firewall? YES Choose Per Processor Licensing NO Is the app intended to be used by a countable # of users? NO Choose Per Processor Licensing YES Is the # of users large enough to justify Per Processor? (See Diagram 3.2 for guidance) YES Choose Per Processor Licensing NO Are most devices used by a single person? YES Choose Server + User s NO Choose Server + Device s for those devices Chapter 3: How Licenses are Counted: Licensing Models for SQL Server 1721 ? Decision Tree 3.2: General Guidance on Choosing a Licensing Model for an Organization Does the org have good internal process for tracking s? NO Is the # of users/devices estimated to be over the break-even threshold? (See Diagram 3.2 for guidance) YES Choose Per Processor Licensing NO YES Choose Server/ and institute an Software Asset Management process for tracking s Are most of the users/ devices already covered by s? NO Follow guidance for single deal (Decision Tree 3.1) YES Choose Server/ and buy s for the remaining users/devices (Consider s for the entire org) Diagram 3.2: How to Calculate Break-even Point for Per Processor Licensing # of Processor licenses required Processor license price X = Total Processor license(s) cost Server license price = Price difference between Processor license and Server license Break-even Point.. = If you require more than this number of s, then Per Processor will cost less price Chapter 3: How Licenses are Counted: Licensing Models for SQL Server 1822 Example 3.2: Break-even Point for Per Processor Licensing: Single Server In this example, we ll calculate the break-even point for a single SQL Server 2008 Enterprise license with two processors based on U.S. Select Plus Level A Estimated Retail Pricing as of December Note: The prices used here are for example only. The actual end customer pricing varies by the channel through which the SQL Server licenses are purchased, and final pricing is set by the reseller. # of Processor licenses required Processor license price = 2 X 23,500 47,000 Total Processor license(s) cost 47,000 Server license price = ,500 Price difference between Processor license and Server license 38,500 Break-even Point = 257 If more than this number of s are required, then Per Processor will cost less price In this case, if the organization requires more than 257 s, then it would cost less to acquire a Processor license. Chapter 3: How Licenses are Counted: Licensing Models for SQL Server 1923 Example 3.3: Break-Even Point for Per Processor Licensing: Multiple Servers In this example, we ll look at which model would be more cost-effective for this deal. The organization will deploy SQL Server 2008 Standard or SQL Server 2008 Enterprise on each of four servers. They have 800 known users accessing the servers, plus anonymous users accessing the Internet server: Internet Server HR Server ERP Server CRM Server Anonymous users 900 known users The Internet server must be licensed Per Processor, because it is accessed by an unknown number of people and devices. For the remaining servers, we can calculate the break-even point for each server (the point where Per Processor becomes more cost-effective than Server/) using the formula from Diagram 3.2. Server SQL Server Edition Processors Processor License Price Server License Price Price Break-even Point (# of Users) HR Standard ERP Enterprise 4 23, CRM Enterprise 2 23, Internet Standard N/A (Must be licensed Per Processor) Break-even point: 860 users Because the break-even point is 860 users and the organization has 900 users it would be more cost-effective to license all four servers in Per Processor mode. Assessing Your Needs The Microsoft Assessment and Planning Toolkit (MAP) makes it easy for you to assess your current IT infrastructure and determine the right Microsoft technologies for their IT needs. MAP is a powerful inventory, assessment, and reporting tool that can run securely in small or large IT environments without requiring the installation of agent software on any computers or devices. The data and analysis provided by this Solution Accelerator can significantly simplify the planning process for migrating to Windows Vista, Microsoft Office 2007, Windows Server 2008, Windows Server 2008 Hyper-V, Virtual Server 2005 R2, SQL Server 2008, and Microsoft Application Virtualization (formerly SoftGrid). Among the detailed analysis information MAP provides are: Hardware and device compatibility for migration to SQL Server 2008, Windows Server 2008, and Hyper-V server virtualization Existing client and server computers where Microsoft SQL Server instances are found Virtual machines (VMs) in the computer environment i For more information, or to download the tool, please visit Chapter 3: How Licenses are Counted: Licensing Models for SQL Server 2024 Chapter 4: How to Count Licenses in Advanced Scenarios Part 1: Virtualization and License Mobility In this Chapter Overview 21 Anatomy of a Virtual Machine 21 Multi-core Processors and Hyper-threading 23 Counting Licenses for VMs (Server/ Model) 24 Standard and Workgroup Editions 24 Counting Licenses for VMs (Per Processor Model) 25 How to Calculate Processor Licenses for a Single VM 26 How to Calculate Processor Licenses for Multiple VMs 28 How to Calculate Processor Licenses for SQL Server Running on VMs and the POSE 31 Server Application License Mobility: Reassigning Licenses and Moving SQL Server Instances within a Server Farm 31 Key Terms Introduced Cores: Processing execution units on a processor Hyper-threading technology (HTT): Allows each core to divide the execution of a computer program into two or more concurrently running tasks, called threads Motherboard: The main circuit board inside of the hardware where processor chips, video cards, and other components are connected, receive power, and communicate with one another Processor: A complete computation unit fabricated on a single chip that performs the work of the computer Socket: Spot on the motherboard where a processor is connected Threads: Concurrently running tasks executing a computer program Virtual Machine (VM): An emulated software version of a computer that executes programs like a separate physical computer Virtual processor: Processor execution unit supporting a VM Overview Microsoft SQL Server is increasingly being deployed in settings that incorporate virtualization, which enables running instances of SQL Server concurrently in separate virtual operating system environments (VOSEs). Examples of server virtualization technologies include Microsoft Windows Server 2008 with Hyper-V and VMWare. How to determine the number of Server licenses or Processor licenses required for SQL Server running in the physical operating system environment (POSE) is explained in Chapter 3. Here we ll look at how to calculate the license requirement when SQL Server is running on a virtual machine (VM). When you are deploying SQL Server on a VM, the license requirements depend upon: The licensing model (Server/ or Per Processor) The edition of SQL Server The characteristics of the physical server and VM(s) on which SQL Server will run Whether hyper-threading is enabled Anatomy of a Virtual Machine Use the diagrams below to familiarize yourself with the characteristics of the VM and physical server that potentially impact the license requirements. Chapter 4: How to Count Licenses for Advanced Scenarios: Part 1 2125 Diagram 4.1: Virtual Machine Running SQL Server Virtual Machine (VM) with SQL Server Running in the VOSE (VM runs on a physical server) Running instance of SQL Server Operating system Virtual OS Environment (VOSE) HTT Physical server Hyper-threading status (on or off) Diagram 4.2: Server Components Motherboard: The main circuit board inside of the hardware where processor chips, video cards, and other components are connected, receive power, and communicate with one another Processor: A complete computation engine that is fabricated on a single chip and performs the work of the computer Socket: Spot on the motherboard where a processor is connected Threads: Divide the execution of a computer program into two or more concurrently running tasks Cores: Processing execution unit on a processor. Multi-core processors contain more than one core. Chapter 4: How to Count Licenses for Advanced Scenarios: Part 1 2226 Multi-core Processors and Hyper-threading When using multi-core processors, each core in the processor essentially acts as a separate processor. Further, Intel s hyper-threading technology (officially called Hyper-Threading Technology or HTT) allows each core to divide the execution of a computer program into two or more concurrently running tasks, called threads of execution or just threads. In these cases, the individual thread essentially acts as a separate processor. When creating VMs, typically each virtual processor is the equivalent of: one core (when hyper-threading is off) one thread (when hyper-threading is on) Diagram 4.3: Mapping Virtual Processors to Cores when Hyper-threading is Off Two virtual processors Dual core physical processor HTT Hyper-threading off Diagram 4.4: Mapping Virtual Processors to Threads when Hyper-threading is On Four virtual processors Dual core physical processor with two threads per core HTT Hyper-threading on Chapter 4: How to Count Licenses for Advanced Scenarios: Part 1 2327 Counting Licenses for VMs (Server/ Model)! Rule 4.1: Count separate blades and partitions on which SQL Server will run as separate servers. Standard and Workgroup Editions When licensing SQL Server Standard or Workgroup for virtualization under the Server/Client Access License () model, each virtual machine (VM) on which SQL Server will run is licensed as if it were a separate physical server. That means When licensing SQL Server Standard or Workgroup for virtualization under the Server/ model: One Server license is required for EACH VM on which SQL Server will run Enterprise Edition Each physical server licensed for SQL Server Enterprise under the Server/ model is also licensed to run SQL Server Enterprise in as many VMs as the hardware will support. So there is no difference between licensing Enterprise edition for physical and virtual environments. When licensing SQL Server Enterprise for virtualization under the Server/ model: One Server license is required for EACH physical server on which SQL Server will run Requirements When licensing SQL Server under the Server/ model, the requirements are the same for virtual operating system environments (VOSEs) as they are for physical operating system environments (POSEs). i For details about licensing SQL Server under the Server/ model, refer to Chapter 3. Chapter 4: How to Count Licenses for Advanced Scenarios: Part 1 2428 Example 4.1: Counting Licenses for VMs (Server/ Model) In this example, an organization is running SQL Server 2008 Standard on two VMs and SQL Server Enterprise on one VM. VM 1 VM 2 VM 3 Under the Server/ model, each VM gets licensed as if it were a separate physical server, therefore the organization needs: Two Server licenses for SQL Server 2008 Standard One Server license for SQL Server 2008 Workgroup SQL Server s as required Counting Licenses for VMs (Per Processor Model) Determining the number of Processor licenses required under the Per Processor model depends not only upon the SQL Server edition, but upon how resources in the server are allocated in support of SQL Server. There are three data points you will want to gather for each VM on which SQL Server will run and the underlying physical machine(s): A. Number of virtual processors supporting the VM B. Number of cores per physical processor (if hyper-threading is off) OR number of threads per physical processor (if hyper-threading is on) C. Number of physical processors With these data points, you can calculate the required number of Processor licenses for a given SQL Server edition by following a simple formula. Note: The instructions provided in this guide assume that: The number of cores or threads in each processor is the same; and If hyper-threading is on, each virtual processor maps to one complete thread. Most scenarios fit these assumptions. For assistance with determining license requirements in rare scenarios that do not fit these assumptions, gather all of the data about the configuration you can, and then contact your Microsoft reseller or account manager. Chapter 4: How to Count Licenses for Advanced Scenarios: Part 1 2529 .. Diagram 4.5: Counting Licenses for VMs (Per Processor Model) With data points A C below, you have the information you need to calculate the number of Processor licenses required for most virtualization scenarios: A. # of virtual processors supporting the VM Virtual machine (VM) B. # of cores per physical processor (if hyper-threading off) or # of threads per physical processor (if hyper-threading in on) C. # of physical processors HTT Physical server Hyper-threading setting (on or off) Below you will find instructions on how to use the data points and formulas to calculate the required Processor licenses for: 1. SQL Server running on a single virtual machine (VM) 2. SQL Server running on multiple VMs 3. SQL Server running on one or more VMs and the physical OS environment (POSE) How to Calculate Processor Licenses for a Single VM For a single VM, you divide data point A (number of virtual processors supporting the VM) by data point B (# of cores [HTT off] or threads [HTT on] per physical processor) to calculate the number of Processor licenses required for any SQL Server edition(s) that will be licensed. If the result is not a whole number, then you round up to the next whole number. Diagram 4.6: Formula for Calculating Processor Licenses Required for a Single VM Round fractions up to the next whole number A B = # of Processor licenses required # of virtual processors supporting the VM # of cores (hyperthreading off) or threads (if hyperthreading on) per physical processor Chapter 4: How to Count Licenses for Advanced Scenarios: Part 1 2630 .... Example 4.2: Calculating Processor Licenses for a Single VM with Hyper-threading Off This example server has two quad-core processors supporting one VM running SQL Server. Hyper-threading is off, so each virtual processor is the equivalent of one core. HTT Using the formula above, calculate the number of Processor licenses required: A 4 B Round fractions up to the next whole number 4 = 1 # of Processor licenses required In this example, just one Processor license is required for any edition. Note: If both of the physical processors are licensed for SQL Server Enterprise, then the software may be run on as many VMs as the hardware and operating system will support. Example 4.3: Calculating Processor Licenses for a Single VM with Hyper-threading On This example server has two single-core processors supporting one VM running SQL Server. Hyper-threading is on, so each virtual processor is the equivalent of one thread. Each core has two threads, so there are two threads per processor. HTT Using data points A and B, calculate the number of Processor licenses required: A 4 B Round fractions up to the next whole number 2 = 2 Number of Processor licenses required Note: If both of the physical processors are licensed for SQL Server Enterprise, then the software may be run on as many VMs as the hardware and operating system will support. Chapter 4: How to Count Licenses for Advanced Scenarios: Part 1 2731 How to Calculate Processor Licenses for Multiple VMs To calculate the Processor licenses required for multiple VMs running SQL Server, calculate the requirements for each VM separately using the same A/B formula, and then add the results for VMs that are running the same edition of SQL Server to get the total number of Processor licenses required for each edition being used. Note: If all of the physical processors (data point C) are licensed for SQL Server Enterprise, then instances of SQL Server may be run on as many VMs as the hardware and operating system will support. That means you never need more Processor licenses than to total number of physical processors. Diagram 4.7: Calculating Processor Licenses for Multiple VMs Calculate the number of Processor licenses required for each individual VM, and then add the results. If different editions of SQL Server will be used, do your calculations in groups by edition to make sure you arrive at the correct number licenses for each edition. VMs that Will Run SQL Server Standard VMs that Will Run SQL Server Web Round up to the next whole number Round up to the next whole number VM 1 A B.. = VM 1 A B.. = VM 2 A B.. = VM 2 A B.. =. VM n A B.. =. VM n A B.. = Total Total # of SQL Server Standard Processor licenses required # of SQL Server Web Processor licenses required VMs that Will Run SQL Server Workgroup VMs that Will Run SQL Server Enterprise Round up to the next whole number Round up to the next whole number VM 1 A B.. = VM 1 A B.. = VM 2 A B.. = VM 2 A B.. =. VM n A B.. =. VM n A B.. = C Total Total # of physical processors # of SQL Server Web Processor licenses required # of SQL Server Enterprise Processor licenses required is LESSER of these Chapter 4: How to Count Licenses for Advanced Scenarios: Part 1 2832 Example 4.4: Calculating Processor Licenses for Multiple VMs with Hyper-threading Off This example server has four quad-core processors supporting four VMs running SQL Server. Hyper-threading is off, so each virtual processor is the equivalent of one core. VM 1 VM 2 VM 3 VM 4 HTT VMs that Will Run SQL Server Standard VMs that Will Run SQL Server Web Round up to the next whole number VM 1 VM 2 A. B A =. B.. = None Total 2 # of SQL Server Standard Processor licenses required VMs that Will Run SQL Server Workgroup VMs that Will Run SQL Server Enterprise VM 3 A. B =.5 None VM 4 A. B = C Total 2 4 # of physical processors # of SQL Server Enterprise Processor licenses required is LESSER of these Under the Per Processor model, this server requires: Two SQL Server Standard Processor licenses Two SQL Server Enterprise Processor licenses No s Note: If all four of the physical processors are licensed for SQL Server Enterprise, then the software may be run on as many VMs as the hardware and operating system will support. Chapter 4: How to Count Licenses for Advanced Scenarios: Part 1 2933 Example 4.5: Calculating Processor Licenses for Multiple VMs with Hyper-threading On This example server has three single-core processors supporting three VMs running SQL Server (and one VM running Microsoft BizTalk Server). Hyper-threading is on, so each virtual processor is the equivalent of one thread. Each core has two threads, so there are two threads per processor. VM 1 VM 2 VM 3 VM 4 HTT VMs that Will Run SQL Server Standard VMs that Will Run SQL Server Web Round up to the next whole number VM 2 A 1 2 =.. B.5 1 None Number of SQL Server Standard Processor licenses required VMs that Will Run SQL Server Workgroup VMs that Will Run SQL Server Enterprise VM 1 A B = 1.. VM 3 A B 2 2 = 1.. C 3 # of physical processors Number of SQL Server Workgroup Processor licenses required # of SQL Server Enterprise Processor licenses required is LESSER of these Under the Per Processor model, this server requires: One SQL Server Standard Processor licenses One SQL Server Workgroup Processor licenses One SQL Server Enterprise Processor license No s Note: If all three of the physical processors are licensed for SQL Server Enterprise, then the software may be run on as many VMs as the hardware and operating system will support. Chapter 4: How to Count Licenses for Advanced Scenarios: Part 1 3034 How to Calculate Processor Licenses for SQL Server Running on VMs and the POSE In some cases, you may want to run SQL Server on the physical operating system environment (POSE) in addition to running SQL Server on VMs. If this is the case, you simply calculate the licenses required for the VMs as explained above, and then license the POSE in the same manner as for any physical server as explained in Chapter 3. Special Consideration for SQL Server Enterprise If SQL Server Enterprise will run in VMs and the POSE, keep in mind that: Under the Server/ model, if the physical server is licensed for SQL Server Enterprise, the software may be run in the POSE and any number of VMs the hardware will support. Likewise, under the Per Processor model, if all processors are licensed, the software may be run in the POSE and any number of VMs the hardware will support. Server Application License Mobility: Reassigning Licenses and Moving SQL Server Instances within a Server Farm For load balancing and dynamic allocation of resources within a server farm, you may want to move instances of SQL Server across servers. Effective September 1, 2008, Microsoft introduced changes to the license rules for moving instances of server software products across server in a server farm. For SQL Server, these rule changes apply to SQL Server 2008 Enterprise only. For other editions, once a SQL Server license is assigned to a specific server, you cannot reassign it to another server and move the running instance of SQL Server within 90 days. To move running instances of SQL Server more often than that, each server would need to have a license assigned to it. Example 4.6: Reassigning Licenses for SQL Server Editions Other Than SQL Server 2008 Enterprise January February March April January 15 You assign a SQL Server 2008 Standard license to server April 16 You may now reassign the license to another server Reassignment of license not permitted. To move running instance of SQL Server during this period, both servers must be licensed. Chapter 4: How to Count Licenses for Advanced Scenarios: Part 1 3135 Reassigning Licenses and Moving Running Instances of SQL Server 2008 Enterprise When properly licensed, running instances of SQL Server 2008 Enterprise may be moved freely across servers within a server farm. (There is no 90 day minimum period before reassignment.) Example 4.7: Reassigning SQL Server 2008 Enterprise Licenses within a Server Farm January February March April January 15 You assign a SQL Server 2008 Enterprise license to server You may reassign SQL Server 2008 Enterprise licenses and move running instances freely within the server farm! Rules 4.2: Server Farms A server farm can consist of up to two data centers each physically located: In time zones that are within four hours of one another (UTC is Coordinated Universal Time), and/or Within the European Union (EU) and/or European Free Trade Association (EFTA) Each data center may be part of only one server farm. You may reassign a data center from one server farm to another, but not on a short-term basis (that is, not within 90 days of the last assignment). Example 4.8: Server Farm Data centers A and B can be in the same server farm because their UTC time zones are within four hours of one another. Data Center C and Data Center D cannot be in the same server farm, because their UTC time zones are not within four hours on one another. 3 hours 5.5 hours Data Center A Seattle, WA, USA UTC -8 hrs Data Center B New York, NY, USA UTC -5 hrs Data Center C London, England UTC +/- 0 hrs Data Center D Bangalore, India UTC +5.5 hrs Server Farm Server Farm Chapter 4: How to Count Licenses for Advanced Scenarios: Part 1 3236 ! Rules 4.3: Moving Instances of SQL Server Enterprise in Server Farms Under the Server/ model, you may run unlimited instances of SQL Server 2008 Enterprise within the server farm, and move those instances freely, as long as those instances are not running on more servers than the number of licenses assigned to the server farm. Under the Per Processor model, you effectively count the greatest number of physical processors that may support running instances of SQL Server 2008 Enterprise at any one time across the server farm and assign that number of Processor licenses (see Diagram 4.7). Once a SQL Server 2008 Enterprise license is assigned to a specific server, you cannot be reassign it to another server outside of the server farm and move the running instance of SQL Server instance within 90 days. Diagram 4.8: Counting Processors Licenses for Server Application Mobility Scenarios If you can be sure that only certain physical processors support running instances for SQL Server 2008 Enterprise, then you only need a Processor license for those physical processors. If you are unable to control which physical processor(s) support running instances of SQL Server 2008 Enterprise (or you do not know), then you need a Processor license for each physical processor. Chapter 4: How to Count Licenses for Advanced Scenarios: Part 1 3337 Example 4.9: Moving SQL Server 2008 Enterprise Instances across Three Servers within a Five Server Farm In this example, we have a server farm with five servers. The organization wants to run instances of SQL Server 2008 Enterprise on a single VM on each of any three servers in the farm at any one time. Multiple instances may be run on licensed servers HTT HTT HTT HTT HTT Server 1 Server 2 Server 3 Server 4 Server 5 License requirements: Server/ Model Three Server licenses SQL s as required Per Processor Model Six Processor licenses, or Three Processor licenses (only if you can be sure that only one physical processor per server is supporting running instances of SQL Server) No SQL Server s required Note: Prior to the implementation of the Application Server License Mobility rule, 10 Processor licenses would have been required to achieve the same flexibility. i For more information, refer to the Server Application Mobility licensing brief at Chapter 4: How to Count Licenses for Advanced Scenarios: Part 1 3438 Chapter 5: How to Count Licenses in Advanced Scenarios Part 2: High Availability, Multiplexing, and Components In this Chapter High Availability/Failover Support 35 Back-up Log Shipping 36 Database Mirroring 39 Failover Clustering 41 Multiplexing/Pooling 43 Using SQL Server Business Intelligence Components on Additional Servers 46 Additional Software That May Be Run 47 Key Terms Introduced Failover: Setting up servers so that if one fails, the other takes over Multiplexing (pooling): The use of hardware and/or software that reduces the number of devices or users that directly access the server software High Availability/Failover Support Microsoft SQL Server can be configured so that if one server fails, its processing will be picked-up, recovered, and continued by the other server. SQL Server 2008 Enterprise, Standard, Web, and Workgroup editions provide three types of failover support: Backup log-shipping Database mirroring Failover clustering Log-shipping and database mirroring take place at the database level, whereas failover clustering takes place at the SQL Server instance level. For detailed information about High Availability solutions, visit: Each failover type and the licensing requirements are described further below. Regardless of which type of failover support is being used, keep the following rules in mind: Chapter 5: How to Count Licenses for Advanced Scenarios: Part 2 3539 Rules 5.1: Failover Basics The server being used for failover does not need to be licensed for SQL Server as long as it is truly passive (not serving SQL Server data to clients or running active SQL Server workloads). If it is serving SQL Server data to clients (such as reports) or running active SQL Server workloads, then it must be licensed for SQL Server. Does not require separate SQL Server license as long as it is not serving data to clients or running SQL Server workloads Active server Passive server For any operating system environment in which you run instances of the server software, you may run up to the same number of passive failover instances in a separate operating system environment. Active server Passive server When licensing SQL Server under the Per Processor model, the number of Processor licenses must be based on the server that requires the higher number of licenses. This way, when the failover server takes over, it is adequately licensed. Processor licenses must be based on passive server, because it has more processors Active server Passive server! Back-up Log Shipping Log shipping allows you to automatically send transaction log back-ups from a primary database on a primary server instance to one or more secondary databases on separate secondary server instances. The transaction log backups are applied to each of the secondary databases individually. An optional third server instance, known as the monitor server, records the history and status of back-up and restore operations and, optionally, raises alerts if these operations fail to occur as scheduled. SQL Server 2008 Standard and Enterprise licenses allow for shipping logs from one primary server instance to one secondary server instance. Chapter 5: How to Count Licenses for Advanced Scenarios: Part 2 3640 ? Decision Tree 5.1: Do I Count Licenses Based on the Active or Passive Server? If the passive server were to be licensed, would it require more licenses than the active server? NO YES License based on the active server License based on the passive server Diagram 5.1: Log-Shipping Configuration 1. Primary server instance transaction log files from primary database to back-up share 2. Secondary server instance copies log files to a local folder 3. Secondary server instance restores log files to local secondary database Primary DB 1 Log Files Back-up share Log Files Secondary DB 1 Does not require separate SQL Server license as long as it is not serving data to clients or running SQL Server workloads Primary server Secondary server Monitor server (optional) Tracks all of the details of log shipping Chapter 5: How to Count Licenses for Advanced Scenarios: Part 2 3741 Diagram 5.2: Log-Shipping from a Single Primary Server to Multiple Secondary Servers Back-up log shipping allows for multiple secondary servers, however, the SQL Server license for the primary server covers only one secondary server. Any additional secondary servers receiving the log file back-ups must be licensed. Primary DB 1 Log Files Back-up share Log Files Secondary DB 1 Does not require separate SQL Server license as long as it is not serving data to clients or running SQL Server workloads Primary server Secondary server 1 Log Files Secondary DB 2 SQL Server license required Secondary server 2 Diagram 5.3: Log-Shipping from Multiple Primary Servers to a Single Secondary Server A single server may act as the secondary server for multiple primary servers. In this case, each primary server instance may ship back-up logs to the secondary server without the need to license the secondary server for SQL Server. Primary DB 1 Log Files Back-up share Log Files Log Files Secondary DB 1 Secondary DB 2 Does not require separate SQL Server license as long as it is not serving data to clients or running SQL Server workloads Primary server 1 Primary DB 2 Log Files Secondary server Primary server 2 Chapter 5: How to Count Licenses for Advanced Scenarios: Part 2 3842 Database Mirroring Each database mirroring configuration involves two servers: Principal server: Contains the principal database and serves the database to clients Mirror server: Contains the mirror database, which is brought continuously up-to-date with the principal database Diagram 5.4: Database Mirroring Principal and Mirror Servers A single server may act as the secondary server for multiple primary servers. In this case, each primary server instance may ship transaction logs to the secondary server without the need to license the secondary server for SQL Server. DB 1 Principal Data flow DB 1 Mirror Principal server Contains the principal database and serves the database to clients Mirror server Contains the mirror database, which is brought continuously up-to-date with the principal database Operation Modes for Database Mirroring Database mirroring runs with either synchronous operation in high-safety mode, or asynchronous operation in highperformance mode: High-safety mode: A committed transaction is committed on both servers, but at the risk of increased transaction latency. This mode provides hot standby server that supports rapid failover without a loss of data from committed transactions. High-performance mode: The transactions commit without waiting for the mirror server to write the log to disk, which maximizes performance. This mode provides a warm standby server (with possible data loss). High-safety mode with automatic failover requires a third server instance, known as a witness. The witness does not serve the database; it supports automatic failover by verifying whether the principal server is up and functioning. Chapter 5: How to Count Licenses for Advanced Scenarios: Part 2 3943 Diagram 5.5: Database Mirroring Configuration A single server may act as the secondary server for multiple primary servers. In this case, each primary server instance may ship transaction logs to the secondary server without the need to license the secondary server for SQL Server. In the case that the principal server fails, the mirror server takes over as the principal. A 30-day grace period is allowed to restore and run SQL Server on the original principal server or license the mirror server (which is now serving as the principal server). DB 1 Principal Data flow DB 1 Mirror Does not require separate SQL Server license as long as it is not serving data to clients or running active SQL Server workloads Principal server Contains the principal database and serves the database to clients Mirror server Contains the mirror database, which is brought continuously up-to-date with the principal database Witness server (optional) Used in high-safety mode with automatic failover to verify whether the principal server is up and functioning Snapshot Reporting The mirror may be used indirectly for reporting by creating a database snapshot on the mirror database. The database snapshot provides clients with read-only access to the data in the database as it existed when the snapshot was created. This functionality, however, requires that the Mirror Server be licensed, as the SQL Server data is being accessed. Diagram 5.6: Database Mirroring with Snapshot Reporting DB 1 Principal Data flow DB 1 Mirror Snapshot reporting Principal server Mirror server License required as mirror server is actively serving data to client in the form of snapshot reports Chapter 5: How to Count Licenses for Advanced Scenarios: Part 2 4044 Failover Clustering Failover clustering provides high-availability support for an entire instance of SQL Server. A failover cluster is a combination of one or more nodes, or servers, with two or more shared disks. SQL Server 2008 Enterprise supports failover clusters with up to 16 nodes. SQL Server 2008 Standard supports 2-node failover clusters. Note: SQL Server Reporting Services reporting components cannot provide failover support when they are clustered. Diagram 5.7: 2-node and n+1 Failover Clusters In a two node cluster, one server (active server) is set-up to failover to the other server (passive server). In an n+1 failover cluster, you have a given number of servers (n) running active SQL Server instances (active servers) all set-up to failover to the same server. In this case the failover (passive) server does not require a separate license because it is not running SQL Server workloads or serving data to clients. 2-node Cluster n+1 Cluster Active server Passive server Active Server 1 Active Server 2 Active Server 3 Passive server Active Server 4 Chapter 5: How to Count Licenses for Advanced Scenarios: Part 2 4145 Diagram 5.8: Failover Cluster with Active Failover Server In this example, Servers 1-4 are set to failover to Server 5, which is also running an active instance of SQL Server (requiring that it be licensed.) Server 5, in turn, is set to failover to Server 4. Server 1 Server 2 Server 3 Server 5 Server 4 Diagram 5.9: Failover Cluster with Each Active Server Set to Failover to another Active Server Each server is acting as the failover server for another server in the cluster and also running an active instance of SQL Server, therefore needs to be licensed. Server 1 Server 2 Server 3 Server 4 Chapter 5: How to Count Licenses for Advanced Scenarios: Part 2 4246 Cold Backups for Disaster Recovery If you have Software Assurance coverage for your SQL Server license are also entitled to the Cold Backups for Disaster Recovery benefit. With this benefit, for each instance of SQL Server run in a physical or virtual operating system environment on a licensed server, you may temporarily run a backup instance in a physical or virtual operating system environment on a server dedicated to disaster recovery.! Rules 5.1: Cold Backups for Disaster Recovery The server must be turned off except for (i) limited software self-testing and patch management, or (ii) disaster recovery. The server may not be in the same cluster as the production server. The backup and production instances may be run at the same time only while recovering the production instance from a disaster. The right to run the backup instances ends when the Software Assurance coverage ends. Multiplexing/Pooling Sometimes organizations develop network scenarios that use various forms of hardware and/or software that reduce the number of devices or users that directly access or use the software on a particular server, often called multiplexing or pooling hardware or software. Use of multiplexing or pooling hardware and/or software does not reduce the number of s required. Remember: If licensing under the Per Processor model, s are not required. Chapter 5: How to Count Licenses for Advanced Scenarios: Part 2 4347 ! Rules 5.2: Multiplexing A SQL and Windows Server are required for each distinct device or user that is connected to the multiplexing or pooling software or hardware front end: With multiplexing Pooling hardware or software Without multiplexing 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 s required: With multiplexing SharePoint portal Pooling hardware or software Without multiplexing Manual transfer of data from employee to employee does not require a 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 (as long as the report does not access a SQL Server in some way): With multiplexing Manual forwarding of reports Pooling hardware or software Without multiplexing Manual forwarding of reports Chapter 5: How to Count Licenses for Advanced Scenarios: Part 2 4448 Example 5.1: Robotic Vehicle Control Application In this example, taken from an actual customer case, a Microsoft partner has developed a solution for controlling robotic forklifts in a warehouse. This custom application connects directly to SQL Server. The forklifts connect via wireless TCP/IP to the application which directs the vehicles. The application also monitors the forklifts, and if errors occur, that data is written back to SQL Server. Custom application Four SQL Server s and four Windows Server s are required (although the forklifts connect indirectly to SQL Server data, they still require s under the Server/ model). Example 5.2: Connecting to SQL Server Data through OLTP Application Running on Oracle Even though the users in Group A are not connecting directly to the SQL Server data warehouse, they still require s. Group A s Required Group B s Required OLTP app on Oracle Data warehouse Chapter 5: How to Count Licenses for Advanced Scenarios: Part 2 4549 Using SQL Server Business Intelligence Components on Additional Servers The Business Intelligence components for SQL Server 2008 include Analysis Services (AS), Reporting Services (RS), and Integration Services (IS). To use any of these components, the server on which the component is installed must have a valid SQL Server license. If these components are running on a separate server than the main database server, then they require an additional license for each additional server on which they are installed. Diagram 5.10: Business Intelligence Component Licensing Any server running a SQL Server BI component must be licensed for SQL Server. Example 5.2: SQL Server BI Components on Different Servers In this example, SQL Server 2008 Enterprise is running on the production server, and SQL Server 2008 Standard Reporting Services and Analysis Services are running on separate servers. Reporting Services Analysis Services Data sources Each server needs to be licensed. If licensing under the Server/ model, you would need one SQL Server 2008 Enterprise license and two SQL Server 2008 Standard licenses. Chapter 5: How to Count Licenses for Advanced Scenarios: Part 2 4650 Example 5.3: SQL Server BI Components on Same Server In this example, SQL Server 2008 Standard is running on the production server, and SQL Server 2008 Standard Reporting Services and Analysis Services are running on the same separate server. Reporting Services Analysis Services Data sources If licensing under the Server/ model, you would need two SQL Server 2008 Standard licenses. Additional Software That May Be Run The license rights for SQL Server 2008 Enterprise, Standard, Web, and Workgroup editions permit without the need for additional licenses the use of the following additional software in any number of virtual or physical operating system environments on any number of devices connecting directly or indirectly to SQL Server: Business Intelligence Development Studio Client Tools Backward Compatibility Client Tools Connectivity Client Tools Software Development Kit Management Studio Microsoft Sync Framework SQL Server 2008 Books Online Chapter 5: How to Count Licenses for Advanced Scenarios: Part 2 4751 Chapter 6: Other Microsoft Products that Run on SQL Server In this Chapter Overview 48 Dynamics ERP 49 Forefront Client Security Management Console 49 Windows SBS and EBS 51 System Center 53 Overview Some Microsoft products run on Microsoft SQL Server for functionality as an enabling technology. In these cases, you often have the option to license SQL Server technology along with the other product license, or to use your separatelyacquired SQL Server licenses. Below is an overview of Microsoft products that use SQL Server as an enabling technology, and your options for acquiring the necessary SQL Server licenses. Table 6.1: How to License SQL Server as an Enabling Technology for Other Microsoft Products Category SQL Server Licensing Options Products 1 2 SQL Server licenses required and must be acquired separately under Server/ or Per Processor models SQL Server licenses required and may be acquired: 1) separately under Server/ or Per Processor models, or 2) with product offering that includes SQL Server technology Microsoft Dynamics CRM Microsoft Office SharePoint Server Dynamics ERP Forefront Client Security Management Console Windows Small Business Server (SBS) Windows Enterprise Business Server (EBS) Microsoft System Center The remainder of this chapter provides additional guidance for choosing from among the licensing options for products that fall into Category 2 in the table above. You will find details about specific product offerings below, but generally this is how to decide whether you should choose the product offering that includes SQL Server when available:? Decision Tree 6.1: Do I Choose the Product Offering that Includes SQL Server? Is the customer already licensed for SQL Server? YES Choose the product offering that DOES NOT include SQL Server NO Does the customer want to use SQL Server to support functions outside of this specific product? YES Choose the product offering that DOES NOT include SQL Server and license SQL Server separately NO Choose the product SKU that includes SQL Server Chapter 6: Other Microsoft Products that Run on SQL Server 4852 Dynamics ERP Dynamics ERP which includes Dynamics AX, Dynamics GP, Dynamics NAV, and Dynamics SL relies upon SQL Server as an enabling technology. Options for Licensing SQL Server for Use With Dynamics ERP If you already have SQL Server licensed, you do not need to acquire additional SQL Server licenses for use with Dynamics ERP. If you do not have SQL Server licensed, you have the following options for licensing SQL Server with Dynamics ERP: Table 6.2: Options for Licensing SQL Server with Dynamics ERP Licensing Options for SQL Server Acquire Dynamics ERP product and Acquire SQL Server Enterprise or Standard Runtime license for each user Acquire Dynamics ERP product and Acquire SQL Server Enterprise or Standard under Per Processor model Acquire Dynamics ERP product and Acquire SQL Server Enterprise or Standard under Server/ model Separate SQL Server s Required? No (Runtime licenses cover users) No Yes Requirements: SQL Server user for every user using Dynamics ERP or SQL Server device s for every device on which Dynamics ERP is installed Notes on SQL Server Use Rights SQL Server may be used solely to support the Dynamics product. SQL Server may be used in accordance with Product Use Rights/Software License Terms for purposes beyond supporting Dynamics ERP product. SQL Server may be used in accordance with Product Use Rights/Software License Terms for purposes beyond supporting Dynamics ERP product. Forefront Client Security Management Console Forefront Client Security Management Console is available on a per server subscription basis through Microsoft Volume Licensing, SQL Server is required. Options for Licensing SQL Server for Use With Forefront Client Security Management Console If you already have SQL Server licensed, you should choose Forefront Client Security Management Console without SQL Server. If you do not have SQL Server licensed, you have the following options for licensing SQL Server with Forefront Client Security Management Console: Chapter 6: Other Microsoft Products that Run on SQL Server 4953 Table 6.2: Options for Licensing SQL Server with Forefront Client Security Management Console Licensing Options for SQL Server Acquire Forefront Client Security Management Console with SQL Server 2005 Technology (Services SL) Acquire Forefront Client Security Management Console (without SQL Server) and Acquire SQL Server Enterprise or Standard under Per Processor model Acquire Forefront Client Security Management Console (without SQL Server) and Acquire SQL Server Enterprise or Standard under Server/ model Separate SQL Server s Required? Notes on SQL Server Use Rights No SQL Server may be used solely to support Forefront Client Security. No Yes Requirements: SQL Server user for every user using Forefront Client Security, or SQL Server device for every device on which Forefront Client Security (the client) and Forefront Client Security Management Console is installed You may run, at any one time, one instance in one physical or virtual operating system environment on one server. You may create and store any number of instances of SQL Server 2005 Technology on any of servers or storage media solely to exercise the right to run an instance of that technology. SQL Server may be used in accordance with Product Use Rights/Software License Terms for purposes beyond supporting Forefront Client Security. SQL Server may be used in accordance with Product Use Rights/Software License Terms for purposes beyond supporting Forefront Client Security. Chapter 6: Other Microsoft Products that Run on SQL Server 5054 Windows SBS and EBS Windows Small Business Server (SBS) 2008 and Windows Essential Business Server (EBS) 2008 are available in two editions: Standard and Premium. The Premium editions include everything in the Standard edition, plus SQL Server 2008 Standard for Small Business 1 and Windows Server 2008 Standard. 1 SQL Server 2005 may be used in place of or in addition to SQL Server 2008 Standard Edition for Small Business subject to the use rights for SBS/EBS 2008 Premium. (All running instances should be in one Microsoft Active Directory domain). Options for Licensing SQL Server for Use With SBS or EBS If you who already have SQL Server and Windows Server licensed appropriately, you should choose the Standard Edition of SBS or EBS. If your do not have SQL Server licensed, you have the following options for licensing SQL Server with SBS: Table 6.3: Options for Licensing SQL Server with SBS Licensing Options for SQL Server Separate SQL Server s Required? Notes on SQL Server Use Rights Acquire SBS Premium No You may run, at any one time, any number of instances of SQL Server 2008 Standard Edition in one physical or virtual OSE within the Windows SBS 2008 domain (not withstanding any hardware or software limitations). Acquire SBS Standard and Acquire SQL Server Enterprise or Standard under Per Processor model Acquire SBS Standard and Acquire SQL Server Enterprise, Standard, or Standard for Small Business under Server/ model Acquire SBS Standard and Acquire SQL Standard for Small Business under Server/ model No Yes Requirements: SQL Server user for every user accessing the server, or SQL Server device for every device accessing the server Yes Requirements: SQL Server Standard for Small Business user or SQL Server user or for every user accessing the server, or SQL Server Standard for Small Business device or SQL Server device for every user accessing the server, or Windows Small Business Server (SBS) 2008 Suite for Premium Users or Devices may be used instead of SQL Server 2008 s to access instances of the server software within an SBS domain SQL Server may be used in accordance with Product Use Rights/Software License Terms for purposes beyond supporting SBS. SQL Server may be used in accordance with Product Use Rights/Software License Terms for purposes beyond supporting SBS. SQL Server Standard for Small Business may be used in accordance with Product Use Rights/Software License Terms for purposes beyond supporting SBS. Chapter 6: Other Microsoft Products that Run on SQL Server 5155 If you do not have SQL Server licensed, you have the following options for licensing SQL Server with EBS: Table 6.4: Options for Licensing SQL Server with EBS Licensing Options for SQL Server Separate SQL Server s Required? Notes on SQL Server Use Rights Acquire EBS Premium No You may run, at any one time, any number of instances of SQL Server 2008 Standard Edition in one physical or virtual OSE within the Windows EBS 2008 domain (not withstanding any hardware or software limitations). Acquire EBS Standard and Acquire SQL Server Enterprise or Standard under Per Processor model Acquire EBS Standard and Acquire SQL Server Enterprise, Standard, or Standard for Small Business under Server/ model Acquire EBS Standard and Acquire SQL Standard for Small Business under Server/ model No Yes Requirements: SQL Server user for every user accessing the server, or SQL Server device for every device accessing the server Yes Requirements: SQL Server Small Business user or SQL Server user or for every user accessing the server, or SQL Server Small Business device or SQL Server device for every user accessing the server, or Windows Essential Business Server (EBS) 2008 Suite for Premium Users or Devices may be used instead of SQL Server 2008 s to access instances of the server software within an EBS domain SQL Server may be used in accordance with Product Use Rights/Software License Terms for purposes beyond supporting EBS. SQL Server may be used in accordance with Product Use Rights/Software License Terms for purposes beyond supporting EBS. SQL Server Standard for Small Business may be used in accordance with Product Use Rights/Software License Terms for purposes beyond supporting EBS. Chapter 6: Other Microsoft Products that Run on SQL Server 5256 System Center SQL Server technology is offered with the following Microsoft System Center products: System Center Configuration Manager System Center Essentials System Center Mobile Device Manager System Center Operations Manager System Center Data Protection Manager (always includes SQL Server) Options for Licensing SQL Server for Use With System Center If you already have SQL Server licensed, you should choose the System Center product offering that does not include SQL Server. If you do not have SQL Server licensed, you have the following options for licensing SQL Server with System Center products: Table 6.5: Options for Licensing SQL Server with System Center Products Licensing Options for SQL Server Acquire System Center product that includes SQL Server (e.g. System Center Configuration Manager with SQL Server 2005 Technology) Acquire System Center Configuration Manager product that does not include SQL Server and Acquire SQL Server Enterprise or Standard under Per Processor model Acquire System Center Configuration Manager product that does not include SQL Server and Acquire SQL Server Enterprise or Standard under Server/ model Separate SQL Server s Required? No No Yes Requirements: SQL Server user for every user with a device, or devices, managed by the System Center product, or SQL Server device for every device managed by the System Center product Notes on SQL Server Use Rights SQL Server may be used solely to support the specific System Center product (e.g. System Center Configuration Manager). SQL Server may be used in accordance with Product Use Rights/Software License Terms for purposes beyond supporting the specific System Center product. SQL Server may be used in accordance with Product Use Rights/Software License Terms for purposes beyond supporting the specific System Center product. Chapter 6: Other Microsoft Products that Run on SQL Server 5357 Chapter 7: Upgrades, Downgrades, and Step-ups In this Chapter Overview 54 Version Upgrades 55 Version Downgrades 55 Edition Step-ups 56 Step-up Pricing 56 Key Terms Introduced Downgrade: Move to a previous version of the software (e.g. from SQL Server 2008 to SQL Server 2005) Step-up: Move from a lower edition to a higher edition of the software (e.g. from SQL Server Standard to SQL Server Enterprise) Upgrade: Move to a newer version of the software (e.g. from SQL Server 2005 to SQL Server 2008) Overview Diagram 7.1 provides an overview of the version upgrade, version downgrade, and edition step-up paths for the Workgroup, Standard, and Enterprise editions of Microsoft SQL Server 2008 and Further details follow. Diagram 7.1: Upgrade, Downgrade, and Step-up Paths SQL Server 2008 Workgroup Edition Step-up SQL Server 2008 Standard SQL Server 2008 Enterprise Version Upgrade Version Downgrade SQL Server 2005 Workgroup Edition SQL Server 2005 Standard Edition SQL Server 2005 Enterprise Edition Version Upgrade Version Downgrade Edition Step-Up What it Means Move from previous version (e.g. SQL Server 2005) to current version (e.g. SQL Server 2008) Deploy earlier version in place of currently-licensed version (per terms of Software License Terms/PUR) Move from lower edition (e.g. Standard) to higher edition (e.g. Enterprise) How to Get It 1. If existing SQL Server license is covered by SA, you are automatically licensed for upgrade to corresponding SQL Server 2008 edition 2. If existing SQL Server license is not covered by SA, you must purchase a new full license for SQL Server 2008 edition you want Downgrade Rights granted for: All licenses acquired through Microsoft Volume Licensing OEM and FPP (retail) versions of SQL Server Enterprise, Standard, and Workgroup 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 or Standard to Enterprise Chapter 7: Upgrades, Downgrades, and Step-ups 5458 Version Upgrades With a version upgrades, you move from a previous version of the software (e.g. Microsoft SQL Server 2005) to a newer version of the software (e.g. SQL Server 2008). The diagram below shows the acceptable paths for upgrading from SQL Server 2005 editions to SQL Server 2008 editions.! Rules 7.1: Version Upgrades Cross-version upgrades: Cross-version instances of SQL Server 2008 are not supported. Version numbers of the Database Engine, Analysis Services, and Reporting Services components must be the same in an instance of SQL Server Cross-platform upgrades: Cross-platform upgrade is not supported. You cannot upgrade a 32-bit instance of SQL Server to native 64-bit. However, you can upgrade a 32-bit instance of SQL Server to the WOW64: the 32-bit subsystem on a 64-bit server as noted in the diagram above. You can also back up or detach databases from a 32- bit instance of SQL Server, and then restore or attach them to an instance of SQL Server (64-bit) if the databases are not published in replication. In this case, you must also re-create any logins and other user objects in master, msdb, and model system databases. Failover upgrades: To upgrade an instance of SQL Server to a SQL Server failover cluster, the instance being upgraded must be a failover cluster. Upgrading on Windows Server 2008 machines: To upgrade SQL Server 2005 to SQL Server 2008 on a computer that is running Windows Server 2008, you must be running SQL Server 2005 SP2. SQL Server 2005 SP1 is not a supported upgrade scenario.? Decision Tree 7.1: How Do I Upgrade? Do you have SA coverage on the SQL Server 2005 license? YES NO Upgrade to the corresponding SQL Server 2008 edition at no additional license charge Order a License (L) or License & SA pack (L/SA) for the corresponding SQL Server 2008 edition Version Downgrades You can acquire SQL Server licenses and run prior versions of SQL Server per the downgrade rights outlined in the Software License Terms and/or Product Use Rights (PUR). In other words, if you are licensed for a SQL Server 2008 edition, you may choose to deploy a corresponding SQL Server 2005 edition in its place.! Rules 7.2: Version Downgrades If the earlier version includes different components, any terms for those components in the agreement that comes with the earlier version apply. Microsoft is not obligated to supply earlier versions. At any time, you may replace an earlier version with your licensed newer version of the software. Chapter 7: Upgrades, Downgrades, and Step-ups 5559 Edition Step-ups With edition step-ups, you move from a lower edition of the product to a higher edition. For SQL Server, Step-up licenses are available to migrate from: Diagram 7.2: SQL Server Edition Step-up Paths OR Licensed with SA for this Step-up to this Licensed with SA for this Step-up to this Step-up Pricing The Step-up License price is the difference between the L/SA price of the higher edition and the L/SA price of the lower edition of the product. To accommodate customers stepping-up at different points in their agreement period, Step-up license SKUs are available for customers with one, two, or three years of SA coverage remaining. Diagram 7.3: Step-up License Payments Year 1 Year 2 Year 3 Acquire License & Software Assurance for Standard Edition Year 1 payment = One third of license plus one year of Software Assurance for the Standard Edition Acquire two-year remaining Step-up License & Software Assurance for Enterprise Edition Year 2 payment = One third of license plus one year of Software Assurance for Standard Edition Year 3 payment = One third of license plus one year of Software Assurance Standard Edition One half of Step-up License & Software Assurance (Enterprise price minus Standard price) Year 1 Payment Year 2 Payment Year 3 Payment The original Standard Edition payments continue after the acquisition of the Step-up License until the end of the agreement term (annual payment of one third of license plus one year of Software Assurance). The Step-up license simply adds the price difference and spreads that price throughout the remaining years of the agreement term. The price of the Step-up License corresponds to the remaining years left in the agreement term. Chapter 7: Upgrades, Downgrades, and Step-ups 56 View more
Licensing Quick Reference Guide Microsoft Internal - Do Not Distribute Exter- Version 1.0 4/28/2010 Introduction Overview This Quick Reference Guide is for people who need to understand the basics of how More information Microsoft SQL Server 2012 Licensing Guide. June 2012
Microsoft SQL Server 2012 Licensing Guide June 2012 Contents Overview...3 SQL Server 2012 Editions...4 How SQL Server 2012 Licenses Are Sold...5 SQL Server 2012 Licensing Models...6 Core-Based Licensing...7 More information Microsoft SQL Server 2014 Licensing Guide
Microsoft SQL Server 2014 Licensing Guide Publish Date: April 1, 2014 Contents 1 Overview 1 SQL Server 2014 Editions 3 How SQL Server 2014 Licenses Are Sold 4 SQL Server 2014 Licensing Models 4 Core-Based More information Microsoft SQL Server 2012 Licensing Guide
Microsoft SQL Server 2012 Licensing Guide Contents Overview...3 SQL Server 2012 Editions...4 How SQL Server 2012 Licenses Are Sold...5 SQL Server 2012 Licensing Models...6 Core-Based Licensing...7 Server+CAL More information Microsoft SQL Server 2014 Virtualization Licensing Guide
Microsoft SQL Server 2012 Virtualization Licensing Guide June 2012 Contents Introduction...4 Quick Overview: Licensing SQL Server 2012 for Virtualization...4 Licensing Individual Virtual Machines...4 Licensing More information SQL Server 2012 Licensing Quick Reference Guide
SQL Server 2012 Licensing Quick Reference Guide Table of Contents Overview...3 SQL Server 2012 Editions...4 SQL Server 2012 Licensing Models...4 Core-Based Licensing...5 Server+CAL Licensing...7 Licensing More information MICROSOFT OPEN PROGRAMS GUIDE. Microsoft Open Programs Guide
Microsoft Open Programs Guide 1 Table of Contents Microsoft Open Programs Overview... 3 Benefits... 3 The Open Program Family... 3 Open Value... 4 Open Value Organization-Wide Option... 4 Open Value Subscription More information Microsoft Windows Server 2008 Licensing Guide. Your Ultimate Quick Reference Resource for Licensing and Pricing
Microsoft Windows Server 2008 Licensing Guide Your Ultimate Quick Reference Resource for Licensing and Pricing m Table of Contents Summary..................................... 2 Windows Server 2008 Client More information Licensing & Pricing FAQ
Licensing & Pricing FAQ Table of Contents DATACENTER AND STANDARD EDITIONS... 4 Q1. What is new in Windows Server 2012?... 4 Q2. What is the difference between Windows Server 2012 Standard edition and More information Transition: Let s have a look at what will be covered.
Welcome to the Microsoft Licensing Overview course, designed for partners preparing to take the Microsoft Licensing Overview assessment. This course introduces you to Microsoft Licensing program and product More information Comprehensive Resource for Licensing and Pricing
1 Comprehensive Resource for Licensing and Pricing Windows Server, System Center, and Forefront Licensing Guide Table of Contents What s New in This Guide 2 Windows Server 2008 R2 Offerings 2 Windows Server More information Your Comprehensive Resource for Licensing and Pricing. Windows Server 2008 R2 Licensing Guide
Your Comprehensive Resource for Licensing and Pricing Windows Server 2008 R2 Licensing Guide m Table of Contents Summary 3 Table of Windows Server 2008 R2 Core Product Offerings 3 License Terms Windows More information Hyper-V Hosting Guidance:
Hyper-V Hosting Guidance: Using and Licensing Microsoft Server Products in Hyper-V Virtual Hosting Scenarios Microsoft Hosting Guidance Monday, January 18, 2010 Version 3.0 The information contained in More information Licensing Microsoft server products for use in virtual environments
Volume Licensing brief Licensing Microsoft server products for use in virtual environments April 2014 Table of Contents This brief applies to all Microsoft Volume Licensing programs. Summary... 2 What More information Licensing Guide for Customers. License Mobility through Microsoft Software Assurance
Licensing Guide for Customers License Mobility through Microsoft Software Assurance Table of Contents Chapter 1: Introduction to cloud services... 1 Cloud adoption and customer needs... 1 IT as a Service: More information Licensing Microsoft server products for use in virtual environments
Volume Licensing brief Licensing Microsoft server products for use in virtual environments Table of Contents This brief applies to all Microsoft Volume Licensing programs. Summary... 2 What s New in this More information Windows Server 2012 R2 Licensing Datasheet
Windows Server 2012 R2 Licensing Datasheet Product overview Windows Server 2012 R2 captures Microsoft s experience of delivering global-scale cloud services to provide an enterprise-class server and cloud More information SPLA Compliance Your Check List!
SPLA Compliance Your Check List! This SPLA Compliance Check List document has been compiled by HP SLMS to assist Service Providers in understanding the program and product licensing rules under Microsoft More information Microsoft Open License
Microsoft Open License TABLE OF CONTENTS Microsoft Open License Overview... 3 Benefits...3 Open License for Public Sector Organizations... 4 Government Organizations... 4 Academic Organizations... 4 Charitable More information Windows Server 2012 Licensing & Pricing FAQ
Windows Server 2012 Licensing & Pricing FAQ Table of Contents WINDOWS SERVER 2012 DATACENTER AND STANDARD EDITIONS... 3 Q1. What is new in Windows Server 2012?... 3 Q2. What is the difference between Windows More information Hyper-V Hosting Guidance:
Hyper-V Hosting Guidance: Using and Licensing Microsoft Server Products in Hyper-V Virtual Hosting Scenarios Hyper-V Hosting Guidance Wednesday, 29 October 2014 Version 2.01 The information contained in More information What s New in this Brief
B r i e f Licensing Microsoft Windows Server 2008 to Run with Virtualization Technologies VMware s ESX Server, VMware s VMotion, Microsoft s System Center Virtualization Machine Manager, and Parallels More information Introduction to Per Core Licensing and Basic Definitions
Volume Licensing brief Introduction to Per Core Licensing and Basic Definitions Table of Contents This brief applies to all Volume Licensing programs. Summary... 1 What s New in This Brief... 1 Definitions... More information SOFTWARE LICENSING ADVISORS LICENSING BRIEF SQL SERVER VIRTUAL SERVER MOBILITY WITHOUT SOFTWARE ASSURANCE
SOFTWARE LICENSING ADVISORS LICENSING BRIEF SQL SERVER VIRTUAL SERVER MOBILITY WITHOUT SOFTWARE ASSURANCE By taking advantage of some lesser-known SQL Server licensing options, customers can significantly More information Microsoft Enterprise Agreement. Program Guide
Microsoft Enterprise Agreement Program Guide 1 Table of Contents Enterprise Agreement Introduction...3 Enterprise Agreement Overview...3 Enterprise Agreement Benefits...3 Enterprise Agreement Program Features...5 More information System Center 2012 R2
Volume Licensing reference guide System Center 2012 R2 System Center 2012 R2 Licensing Guide (i) Introduction This guide can help Microsoft Volume Licensing customers understand how Microsoft System Center More information BizTalk Server 2013 R2 Licensing Datasheet and FAQ Published: May, 2014
BizTalk Server 2013 R2 Licensing Datasheet and FAQ Published: May, 2014 Product Overview BizTalk Server (BTS) is Microsoft s integration and connectivity server solution. A mature product on its eighth More information The Software Licensing Advisors Guide to Microsoft Software Assurance Rights
www.msftadvisors.com The Software Licensing Advisors Guide to Microsoft Software Assurance Rights This guide summarizes Software Assurance (SA) benefits that are described in multiple Microsoft documents, More information Windows Server 2012 R2 Licensing Datasheet
Windows Server 2012 R2 Licensing Datasheet Product overview Windows Server 2012 R2 captures Microsoft s experience of delivering global-scale cloud services to provide an enterprise-class server and cloud More information BizTalk Server 2013 R2 Licensing Datasheet and FAQ Published: July, 2014
BizTalk Server 2013 R2 Licensing Datasheet and FAQ Published: July, 2014 Product Overview BizTalk Server (BTS) is Microsoft s integration and connectivity server solution. A mature product on its eighth More information License Mobility through Software Assurance
License Mobility through Software Assurance FREQUENTLY ASKED QUESTIONS FOR PARTNERS License Mobility through Software Assurance gives customers the ability to deploy certain Server Application licenses More information BizTalk Server 2013 Licensing Datasheet and FAQ Published: March, 2013
BizTalk Server 2013 Licensing Datasheet and FAQ Published: March, 2013 Product Overview BizTalk Server (BTS) is Microsoft s integration and connectivity server solution. A mature product on its eighth More information System Center 2012 Server Management Licensing... 2
Contents System Center 2012 Server Management Licensing... 2 1. What s new with System Center 2012 licensing?... 2 2. Can you describe the product editions offered with System Center 2012?... 2 3. How More information Microsoft licensing overview. Mikhail Rossiev Licensing Manager, EPG
Microsoft licensing overview Mikhail Rossiev Licensing Manager, EPG What is a License? A software license is the legal right to install, use, access, display, run, or otherwise interact with a software More information Comprehensive Resource for Licensing and Pricing
1 Comprehensive Resource for Licensing and Pricing Windows Server, System Center, and Forefront Licensing Guide Table of Contents What s New in This Guide 2 Windows Server 2008 R2 Offerings 2 Windows Server More information Enrollment for Education Solutions
Enrollment for Education Solutions OFFERING OVERVIEW Introducing the Enrollment for Education Solutions (EES) from Microsoft Volume Licensing Enrollment for Education Solutions (EES) is an easy, cost-effective More information ICONICS Choosing the Correct Edition of MS SQL Server
Description: This application note aims to assist you in choosing the right edition of Microsoft SQL server for your ICONICS applications. OS Requirement: XP Win 2000, XP Pro, Server 2003, Vista, Server More information Program Guide. Server and Cloud Enrollment (SCE)
Program Guide Server and Cloud Enrollment (SCE) Contents How the Server and Cloud Enrollment Works... 3 Available Software and Cloud Services... 4 Core Infrastructure... 4 Application Platform... 4 Developer More information LICENSING MANAGEMENT SERIES. A Guide to Assessing Windows Server Licensing
LICENSING MANAGEMENT SERIES A Guide to Assessing Windows Server Licensing July 2010 This document provides customers of Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, and Windows Server More information Services Provider Use Rights
Microsoft Volume Licensing Services Provider Use Rights Worldwide English January 2015 TABLE OF CONTENTS INTRODUCTION... 2 UNIVERSAL LICENSE TERMS... 5 PER PROCESSOR LICENSE MODEL... 11 Core Infrastructure More information LICENSING MANAGEMENT SERIES. A Guide to Assessing Exchange Server Licensing
LICENSING MANAGEMENT SERIES A Guide to Assessing Exchange Server Licensing April 2012 This document gives Microsoft Volume Licensing customers an overview of licensing for Microsoft Exchange Server 2010, More information Enrollment for Education Solutions
Enrollment for Education Solutions Introducing the Enrollment for Education Solutions (EES) from Microsoft Volume Licensing Enrollment for Education Solutions (EES) is an easy, cost-effective licensing More information Guide to Microsoft Volume Licensing. Guide to Microsoft Volume Licensing
Guide to Microsoft Volume Licensing March 2013 i Table of Contents Chapter 1: Introduction to Microsoft Volume Licensing... 1 How to Use This Guide... 1 Keys to Understanding Microsoft Volume Licensing... More information Services Provider Use Rights
Microsoft Volume Licensing Services Provider Use Rights Worldwide English August 2012 1 TABLE OF CONTENTS INTRODUCTION... 2 UNIVERSAL LICENSE TERMS... 4 PER PROCESSOR LICENSE MODEL... 10 BizTalk Server More information HP Windows Server 2008R2 OEM licenses are available for purchase from HP or your local authorized reseller.
Overview Windows Server 2008 R2 builds on the award-winning foundation of Windows Server 2008, expanding existing technology and adding new features to enable organizations to increase the reliability More information Microsoft Open License. Program Guide
Microsoft Open License Program Guide 1 Table of Contents Understanding Your Licensing Options...3 Microsoft Open License Overview...3 Benefits...3 The Open License Program Family...4 Open Value...4 Open More information Q. How many instances may I run with a license of SBS 2011 Essentials?... 7. Q. How many users can use the SBS 2011 Essentials software?...
Licensing FAQ Table of Contents SBS 2011 Essentials... 7 Q. How many instances may I run with a license of SBS 2011 Essentials?... 7 Q. How many users can use the SBS 2011 Essentials software?... 7 Q. More information Microsoft Volume Licensing Reference Guide
Microsoft Volume Licensing Reference Guide February 2010 Contents CHAPTER 1: Introduction to Volume Licensing... 3 Keys to Understanding Microsoft Volume Licensing... 3 How to Use This Guide... 7 CHAPTER More information Services Provider Use Rights
Microsoft Volume Licensing Services Provider Use Rights Worldwide English April 2014 1 TABLE OF CONTENTS INTRODUCTION... 2 UNIVERSAL LICENSE TERMS... 4 PER PROCESSOR LICENSE MODEL... 10 BizTalk RFID 2010 More information Sage 300 ERP 2014 Compatibility guide
Sage 300 ERP 2014 Compatibility guide 03 17 2014 Table of contents 1.0 Overview 3 1.1 Overview 3 1.1.1 Unlisted platforms are not supported 3 1.1.2 Product updates and program fixes 3 1.1.3 Compatibility More information Q. How many instances may I run with a license of SBS 2011 Essentials?... 7. Q. How many users can use the SBS 2011 Essentials software?...
Licensing FAQ SBS 2011 Essentials... 7 Q. How many instances may I run with a license of SBS 2011 Essentials?... 7 Q. How many users can use the SBS 2011 Essentials software?... 7 Q. I am running SBS 2011 More information Subscription Licensing Guide
Microsoft Dynamics GP 2013 and Microsoft Dynamics NAV 2013 R2 Subscription Licensing Guide January 2014 Partner Edition Microsoft Dynamics GP 2013 and Microsoft Dynamics NAV 2013 R2 Subscription Licensing More information Microsoft Dynamics NAV 2015. Licensing Guide. Microsoft Dynamics NAV 2015 Licensing Guide October 2014 Page 1
Microsoft Dynamics NAV 2015 Licensing Guide Microsoft Dynamics NAV 2015 Licensing Guide October 2014 Page 1 October 2014 Using This Guide Use this guide to improve your understanding of how to license More information SQL Server 2012 Licensing Datasheet & FAQ
SQL Server 2012 Licensing Datasheet & FAQ Published: March 7, 2012 Product Overview SQL Server 2012 is a significant product release, providing Mission Critical Confidence with greater uptime, blazing-fast More information Program Guide. Enterprise Agreement
Program Guide Enterprise Agreement Table of Contents The Microsoft Enterprise Agreement...1 How the Enterprise Agreement Works...1 Purchasing Through Enrollments...1 Enterprise Enrollment... 1 Server and More information How Customers Are Cutting Costs and Building Value with Microsoft Virtualization
How Customers Are Cutting Costs and Building Value with Microsoft Virtualization Introduction The majority of organizations are incorporating virtualization into their IT infrastructures because of the More information QuickSpecs. HP Session Allocation Manager Software (SAM v2.3) Overview
Overview Introduction A key component of the HP Virtual Client Essentials software portfolio, Session Allocation Manager (SAM) administrative software brokers network connections to seamlessly deliver More information Microsoft Software Assurance Academic Customer Guide
Microsoft Software Assurance Academic Customer Guide A reference guide to Software Assurance offerings for Microsoft Academic Volume Licensing programs Software Assurance Customer Guide 1 2003 Microsoft More information NOTE: For more information on HP's offering of Windows Server 2012 R2 products, go to: http://www.hp.com/go/ws2012r2
Overview Windows Server 2012 R2 captures Microsoft's experience of delivering global-scale cloud services to provide an enterprise-class server and cloud platform. It lets you optimize performance for More information Microsoft Volume Licensing Reference Guide
Volume Licensing Guide iii Table of contents Chapter 1: Introduction to Microsoft Volume Licensing... 1 How to use this guide... 1 Keys to understanding Microsoft Volume Licensing... 1 Programs for your More information 1 System Center 2012 Licensing Changes In Plain English
1 System Center 2012 Licensing Changes In Plain English System Center 2012 Licensing Changes In Plain English Revision 1 5/30/2012 Windows Server and System Center portions applicable to all licensing More information Licensing Windows for VDI Environments
Microsoft VDI Suites and Windows VDA Frequently Asked Questions Licensing Windows for VDI Environments How does Microsoft license Windows for virtual environments? Microsoft licenses Windows for virtual More information Licensing Windows for VDI Environments
Licensing Windows for VDI Environments What licensing changes has Microsoft announced? Microsoft has announced the following licensing changes for virtual desktops that will come into effect on July 1st, More information Volume Licensing reference guide. Windows 8 and Windows RT
Volume Licensing reference guide Windows 8 and Windows RT Table of Contents Introduction... 1 Windows 8 Editions, Windows RT, and Related Products... 2 Windows 8 Editions and Windows RT... 2 Windows Desktop More information SPLA Licensing Guide. Microsoft Dynamics GP 2013 and Microsoft Dynamics NAV 2013
Microsoft Dynamics GP 2013 and Microsoft Dynamics NAV 2013 SPLA Licensing Guide Microsoft Dynamics GP 2013 and Microsoft Dynamics NAV 2013 SPLA Licensing Guide January 2014 Page 1 January 2014 Using This More information Sage 300 2016. Compatibility guide. Last revised: October 26, 2015
Sage 300 2016 Compatibility guide Last revised: October 26, 2015 This is a publication of Sage Software, Inc. Copyright 2015. Sage Software, Inc. All rights reserved. Sage, the Sage logos, and the Sage More information Microsoft Enterprise Agreement. Program Guide
Microsoft Enterprise Agreement Program Guide 1 Table of Contents Enterprise Agreement Introduction...3 Enterprise Agreement Benefits...3 Enterprise Agreement Overview...4 Enterprise Agreement Program Features...5 More information Microsoft Dynamics GP 2015. Licensing Guide. Microsoft Dynamics GP 2015 Licensing Guide December 2014 Page 1
Microsoft Dynamics GP 2015 Licensing Guide Microsoft Dynamics GP 2015 Licensing Guide December 2014 Page 1 December 2014 Using This Guide Use this guide to improve your understanding of how to license More information SQL Server 2012 Licensing Datasheet
SQL Server 2012 Licensing Datasheet Published: December 1, 2011 Product Overview SQL Server 2012 is a significant product release, providing Mission Critical Confidence with greater uptime, blazing-fast More information Windows 8.1 and Windows RT 8.1
Volume Licensing reference guide Windows 8.1 and Windows RT 8.1 December 2014 1 Table of Contents Windows 8.1 Editions, Windows RT 8.1, and Related Products... 3 Windows 8.1 Editions and Windows RT 8.1... More information Licensing Microsoft Server Products in Virtual Environments August 2008
B r i e f Licensing Microsoft Products in Virtual s August 2008 Corporate Academic Open License Open License Value Select License Academic Select Enterprise Agreement Summary The purpose of this white More information Microsoft Services Provider License Agreement Program
Microsoft Services Provider License Agreement Program PROGRAM GUIDE Table of Contents Introduction... 3 What Is a Service Provider?... 3 Benefits... 4 Program Eligibility and Requirements... 4 Eligibility More information System Center 2012 R2 Licensing Datasheet
Licensing Datasheet Product Overview Microsoft offers solutions for managing datacenter resources, private clouds, and client devices. Private Cloud/ Management helps your organization achieve IT as a More information Enrollment for Education Solutions (EES)
Volume Licensing Guide Enrollment for Education Solutions (EES) March 2014 i Table of Contents Introduction... 1 Content Specific to Individual Contract Options... 1 Academic Volume Licensing Overview... More information Microsoft Enterprise Agreement
Microsoft Enterprise Agreement TABLE OF CONTENTS Introduction... 3 Enterprise Agreement Introduction... 3 Enterprise Agreement Benefits... 4 Program Features... 5 Enterprise Products... 5 Additional Products... More information Microsoft Visual Studio 2010 Licensing
Microsoft Visual Studio 2010 Licensing White Paper Published February 2010 For the latest information, go to: www.microsoft.com/vstudio The information contained in this document represents the current More information Program Guide. Enterprise Agreement
Program Guide Enterprise Agreement Table of Contents The Microsoft Enterprise Agreement... 1 How the Enterprise Agreement Works... 1 Purchasing through Enrollments... 1 Enterprise Enrollment...1 Enrollment More information for Virtualized Server Environments
for Virtualized Server Environments info@aid.com www.aid.com Understanding Microsoft Licensing (Server Virtualization) 2 PRESENTATION. 1 Past : Role of ITAM in Virtualization Projects / Environments 3 More information Sage ERP Accpac. Compatibility Guide Version 6.0. Revised: November 18, 2010. Version 6.0 Compatibility Guide
Sage ERP Accpac Compatibility Guide Version 6.0 Revised: November 18, 2010 Version 6.0 Compatibility Guide i Contents Overview... 1 Version 6.0 Compatibility... 2 All Environments... 2 Virtual Environments... More information ACTIVE MICROSOFT CERTIFICATIONS:
Last Activity Recorded : August 04, 2011 Microsoft Certification ID : 483228 KENT NORDSTROM Asbergsvagen 27 Soderhamn, 82637 SW kent@xpservices.se ACTIVE MICROSOFT CERTIFICATIONS: Microsoft Certified Solutions More information Services Provider Use Rights
Microsoft Volume Licensing Services Provider Use Rights Worldwide English April 2013 1 TABLE OF CONTENTS INTRODUCTION... 2 UNIVERSAL LICENSE TERMS... 4 PER PROCESSOR LICENSE MODEL... 10 BizTalk Server More information Services Provider Use Rights
Microsoft Volume Licensing Services Provider Use Rights Worldwide English October 2011 1 TABLE OF CONTENTS INTRODUCTION... 2 UNIVERSAL LICENSE TERMS... 4 PER PROCESSOR LICENSE MODEL... 9 BizTalk Server More information Microsoft Product List
Microsoft Product List October 1 2012 The Microsoft Product List provides information monthly about Microsoft software and Online Services licensed through Microsoft Volume Licensing programs. 2012 Microsoft More information SOFTWARE LICENSING ADVISORS SOFTWARE LICENSING ADVISORS LICENSING BRIEF LICENSING BRIEF SQL SERVER PROCESSOR-TO-CORE LICENSING CONVERSION
SOFTWARE LICENSING ADVISORS SOFTWARE LICENSING ADVISORS LICENSING BRIEF LICENSING BRIEF SQL SERVER PROCESSOR-TO-CORE LICENSING CONVERSION The migration of SQL Server from per-processor to per-core licensing More information Licensing Windows for Virtual Desktops
Licensing Windows for Virtual Desktops This document is intended to explain licensing Windows virtual desktops and how to calculate the number of licenses required for common usage scenarios. Contents More information Subscription Licensing Guide
Microsoft Dynamics GP 2013 and Microsoft Dynamics NAV 2013 R2 Subscription Licensing Guide April 2014 Partner Edition Microsoft Dynamics GP 2013 and Microsoft Dynamics NAV 2013 R2 Subscription Licensing More information SharePoint Server for Business Intelligence
SharePoint Server for Business Intelligence SharePoint Business Intelligence Content Team Summary: Step-by-step, learn how to install and configure SharePoint Server 2010 and SQL Server 2008 to create More information Subscription Licensing Guide
Microsoft Dynamics GP 2013 and Microsoft Dynamics NAV 2013 R2 Subscription Licensing Guide January 2014 Partner Edition Microsoft Dynamics GP 2013 and Microsoft Dynamics NAV 2013 R2 Subscription Licensing More information ACTIVE MICROSOFT CERTIFICATIONS:
Last Activity Recorded : December 19, 2014 Microsoft Certification ID : 2665612 MARC GROTE Wittorfer Strasse 4 Bardowick, Lower Saxony 21357 DE grotem@it-training-grote.de ACTIVE MICROSOFT CERTIFICATIONS: More information Client Access Licenses Suite Bridges Overview
Volume Licensing brief Self-Hosted Applications Table of Contents Summary... 1 What s New in This Brief... 1 Details... 1 Licensing Options for Self-Hosted ISVs... 1 What is a Qualified Unified Solution?... More information Volume Licensing Product Terms Explained
Volume Licensing Product Terms Explained Product Terms Explained Table of Contents Introduction... 1 Overview... 1 Using This Guide... 1 Key Terms and Acronyms... 1 Licensing Basics... 2 What Is Intellectual More information Windows 8.1 and Windows RT 8.1
Volume Licensing reference guide Windows 8.1 and Windows RT 8.1 October 2013 1 Table of Contents Introduction... 3 Windows 8.1 Editions, Windows RT 8.1, and Related Products... 4 Windows 8.1 Editions and More information The Windows Server family of products
The Windows Server family of products Regardless of the size and stage of your company, Windows Server solutions will help you reach the next step to success. With products designed to meet the varying More information Frequently Asked Questions. Simplify PC management. Magnify insight. Reviewers Guide
Frequently sked uestions Simplify PC management. Magnify insight. Reviewers Guide 1 FREUENTLY SKED UESTIONS Things you need to know. This document is designed to arm you with key information and links More information QuickSpecs Microsoft Windows Server 2008
Microsoft Windows Server 2008 is Microsoft's next generation operating system designed to be the most flexible and robust Windows Server operating system to date. Windows Server 2008 provides powerful More information 2017 © DocPlayer.net Privacy Policy | Terms of Service | Feedback