SQL Server Licensing Overview

1
SQL Server Licensing Overview

• December 12, 2006
• SQL Server Users Group Meeting

2
Discussion Topics

• SQL Server 2005 Licensing Models
• Multiplexing
• High Availability
• Virtualization and Multi-Instancing
• Additional Software
• Developer Edition
• SQL Server Technology Licensing
• SPLA Program
• Acquiring Licenses via ISV/ASPs
• Downgrade Rights for Previous Versions
• Software Assurance

3
SQL Server 2005 Licensing Models
4
SQL Server Licensing Models

• Per Processor
• License required for each physical or virtual
  processor accessed by an operating system
  environment running SQL Server.
• Does not require any device or user client access
  licenses (CALs).
• Per Server/Per CAL
• Server license required for each operating system
  environment running an instance of SQL Server.
• Device or User CAL for each client device or user
  that accesses a system running SQL Server.

5
Per Processor

• Physical Processors license for each physical
  processor that the physical operating system
  environment uses.
• Virtual Processors license for each virtual
  processor that each of those virtual operating
  system environments uses. If a virtual operating
  system environment uses a fraction of a virtual
  processor, the fraction counts as a full virtual
  processor.

6
Per Processor

• Access unlimited user or device access
• Multicore Processors - regardless of number of
  cores SQL is licensed per processor not per core
• Processor Platform regardless of the processor
  type (32 bit, 64 bit, and IA64) SQL license is
  not platform specific but number of processors a
  function of the edition.
• Product Availability processor licenses
  available for Enterprise, Standard, and Workgroup
  Editions.

7
Per Server/Per CAL

• Access determined by number of CALs
• Processor Platform regardless of the processor
  type (32 bit, 64 bit, and IA64) SQL license is
  not platform specific but number of processors a
  function of the edition.
• Product Availability processor licenses
  available for Enterprise, Standard, and Workgroup
  Editions.

8
Per Server/Per CAL

• When is a CAL needed?
• You must acquire and assign a CAL to each device
  or user that accesses your instances of the
  server software directly or indirectly.
• You do not need CALs for
• Any servers licensed to run instances of the
  server software, and
• Up to two devices or users to access instances of
  the server software only to administer those
  instances.
• Versions CALs permit access to instances of
  earlier versions, but not later versions, of the
  server software.

9
Per Server/Per CAL

• Available Product CALs
• SQL CAL - Can be used with any licensed server
  running SQL Server regardless of the platform (32
  bit, 64 bit, and IA64) and edition (Enterprise,
  Standard, or Workgroup).
• Workgroup CAL Can be used only with a licensed
  SQL Server Workgroup Edition server.
• Available License Types User or Device CALs

10
Packaging Pricing
Express
Workgroup
Standard
Enterprise
Complete data management analysis platform for
medium businesses and large departments
Fully integrated data management and analysis
platform for business critical enterprise
applications
Easiest to use most affordable database
solution for smaller departments growing
businesses
Fastest way for developers to learn, build
deploy simple data driven applications
3,899K per proc or 739 (Server 5 users)
5,999K per proc or 2,799 (Server 10 users)
24,999K per proc or 13,499K (Server 25 users)
Free
11
Multiplexing
12
Multiplexing

• Multiplexing. Hardware or software you use to
• Pool connections,
• Reroute information,
• Reduce the number of devices or users that
  directly access or use the product, or
• Reduce the number of devices or users the product
  directly manages,

Does not reduce the number of licenses of any
type that you need.
13
High Availability
14
High Availability

• Failover Support
• Ability to run up to the same number of passive
  fail-over instances in a separate operating
  system environment for temporary support.
• Passive servers do not need a license.
• Number of processors must not exceed the number
  of processors used in the corresponding operating
  system environment in which the active instances
  are running.
• May run the passive fail-over instances on a
  server other than the licensed server.
• Three types of failovers database mirroring,
  failover clustering, and backup log-shipping.

15
Virtualization and Multi-Instancing
16
Virtualization and Multi-Instancing

• Creating and Storing Instances on Your Servers or
  Storage Media.
• You may create any number of instances of the
  server software and additional software.
• You may store instances of the server software
  and additional software on any of your servers or
  storage media.
• You may create and store instances of the server
  software and additional software solely to
  exercise your right to run instances of the
  server software under any of your software
  licenses as described above (e.g., you may not
  distribute instances to third parties).

17
Virtualization and Multi-Instancing

• Licensing Per Processor
• A license is needed for each running instance on
  a virtual processor
• Virtual processors considered to have the same
  number of threads and cores as each physical
  processor
• Each virtual operating environment containing a
  running instance of SQL can have an unlimited
  number of instances
• Licensing Per Server
• A license is needed for each virtual operating
  system environment containing a running instance
  of SQL
• Each virtual operating environment containing a
  running instance of SQL can have an unlimited
  number of instances

18
Virtualization and Multi-Instancing

• Assigning the License to the Server.
• Before you run any instance of the server
  software you must assign that license to one of
  your servers.
• You may not assign the same license to more than
  one server.
• You may reassign a software license, but not on a
  short-term basis (i.e., not within 90 days of the
  last assignment).
• You may reassign a software license sooner if you
  retire the licensed server due to permanent
  hardware failure.

19
Additional Software
20
Running Instances of the Additional Software
Run or otherwise use any number of instances of
the additional software in physical or virtual
operating system environments on any number of
devices.

• Business Intelligence Development Studio
• Connectivity Components
• Legacy Components
• Management Tools
• Reporting Services Report Manager
• Reporting Services Shared Tools
• Software Development Kit
• SQL Server 2005 Shared Tools
• SQL Server 2005 Books Online
• SQL Server Mobile Server Tools
• SQLXML Client Features

21
SQL Server Developer Edition
22
SQL Server Developer Edition

• Installation and Use Rights.
• General. One user may install and use copies of
  the software to design, develop, test and
  demonstrate your programs. Testing does not
  include staging on a server in a production
  environment, such as loading content prior to
  production use.
• Additional Licensing Requirements and/or Use
  Rights.
• User Testing. End users may access the software
  to perform acceptance tests on your programs.
• Distributable Code. You may use Distributable
  Code as described in the Universal License Terms.
  
• Downgrade. The licensed user may run a prior
  version in place of the licensed version for any
  copy run.

23
License Terms for SQL Server 2005 Technology
24
License Terms for SQL Server 2005 Technology

• Some server products include SQL Server 2005
  Technology (e.g., MOM and SMS)
• Can run, at any one time, one instance of that
  technology in one physical or virtual operating
  system environment on one server solely
  to support that software.
• Do not need SQL Server CALs for that use.
• May create and store any number of instances of
  SQL Server Technology on any of your servers or
  storage media

25
Service Provider License Agreement
26
Service Provider License Agreement (SPLA)

• What is SPLA?
• SPLA is an agreement with Microsoft that enables
  an organization to license Microsoft products and
  use them to provide software services to its
  customers.
• Software Services are services that an
  organization provides to its customers to make
  available, display, run, access, or otherwise
  interact with the licensed products.
• These services may be provided from one or more
  data centers through the Internet, a telephony
  network or a private network on a rental,
  subscription or services basis, whether or not
  the services provider receives a fee.
• Software services exclude any services involving
  an installation of a Microsoft licensed product
  directly on any device to permit a customer to
  interact with the Microsoft licensed product.
• Why SPLA?
• Volume licensing does not cover commercial
  hosting services which occurs when a fee is
  charged to access the software or when the
  software is being provided to a third party to
  use as part of its business.

27
Service Provider License Agreement (SPLA)

• When is SPLA applicable?
• When you provide customer direct or indirect
  access to Microsoft products, such as hosted
  websites or Line of Business (LOB) applications
  through Microsoft server software.
• Direct and indirect access occurs when
• The organization facilitates its customers
  business (including business transactions with
  third parties) through software services or
• The organization provides its customer with
  access to and usage of any application (Microsoft
  or otherwise), and the application is running on
  a server and interacts with a licensed Microsoft
  product on that server.

28
Acquiring Licenses through ISVs/VARs

• Typically use rights are restricted to the
  version and edition included in the license
  provided
• Pricing could be lower than volume licensing
• Maintenance may or may not be available through
  the ISV/VAR
• Licenses cannot be added to a volume license
  agreement for ongoing maintenance

29
Downgrade Rights
30
Downgrade Rights

• Customers can acquire SQL Server 2005 licenses
  and run prior versions of SQL Server per
  downgrade rights outlined in the EULA and Product
  Use Rights documents.
• Customers can install SQL Server 2005 on the same
  server the license is assigned to at a later
  date.
• Use rights are based on the version and edition
  that is acquired not what is installed.

31
Software Assurance
32
Software Assurance Server Benefits
33
Questions?