Blog

SQL Server 2012 Licensing



Just when you think Microsoft licensing is straightforward and you’ve got a pretty good grasp on it, along comes SQL Server which has historically been the exception to the licensing rules.  However with SQL Server 2012 Microsoft has done a great deal of simplification so it’s easy to understand the basics.  You’re going to approach licensing differently depending on whether you’re deploying SQL Server in a physical or virtual environment.

SQL Server Licensing in a physical environment.

SQL Server is available is three main editions; Standard, Business intelligence and Enterprise.  The Enterprise edition is licensed per core (no CALs required), Business Intelligence is licensed per server and client access licence (CALs) and the Standard edition can be licensed using either method.  This is summarised below.

SQL2012Editions

 

Before I present a little flowchart which might make you decision easier, let me clarify a few things about per-core licensing.  We are talking per-core here and not per-physical processor, unlike Windows Server 2012.  Currently SQL Server 2012 and BizTalk Server 2013 are the only Microsoft products licensed per-core.

To find out the appropriate number of cores you need to licence, simply count the number of cores in each physical processor in the physical server.  Software partitioning doesn’t reduce the number of cores you need to licence. Once you have that you need to remember three things:

1. You need a minimum of four core licences per processor.  So if you have a dual-core, dual-processor machine you would need to count that server as a dual, four-core processor and purchase licences for eight cores, despite only having four cores in total.

2. SQL Server 2012 core licences are sold in packs of two: each SKU covers two processors.  So in our example above we would purchase four SQL Core licence SKUs to cover eight cores.

3. Certain AMD processors need to have a multiplication factor of 0.75 applied to the core count.  See this link for the processors in question and what to do.

For server and CAL, SQL Server works in the same way as any other Microsoft server + CAL product.  Licence the server(s), determine the number of unique users and/or devices accessing the SQL Server and purchase the appropriate number and type of CALs.  SQL 2012 CALs will allow access to all previous versions of SQL Server.  Also you don’t require a separate CAL for every SQL Server; a SQL Server 2012 CAL allows access to all the SQL Servers within the organisation.

A simple way of determining the edition and licensing of SQL Server 2012 is below.

SQLEditionFlowchart

 

SQL Server Licensing in a virtual environment.

Regular readers of the licensing blog will be saying “I bet this has something to do with Software Assurance (SA)”.  Well, you’re partly correct.  I’m going to assume you’re running Windows Server 2012 Datacenter edition on these boxes just for simplicity and I haven’t included details of the VOSE OS.

For SQL Server Standard and Business Intelligence editions you can licence individual virtual machines (VMs) using the server + CAL model.  Simply purchase one server license for each VM running SQL Server software, regardless of the number of virtual processors allocated to the VM. Then purchase the appropriate number of CALs.

For example, a customer who wants to deploy the Business Intelligence edition running in six VOSEs, each allocated with four virtual cores, would need to assign six SQL Server 2012 Business Intelligence server licences to that server, plus the CALs to allow access.

For SQL Server Standard and Enterprise editions you can licence individual VMs using the per-core model.  Similar to physical OSEs, all virtual cores supporting virtual OSEs that are running instances of SQL Server 2012 must be licensed.  Customers must purchase a core license for each virtual core (aka virtual processor, virtual CPU, virtual thread) allocated to the VOSE.  Again, you are subject to the four core minimum, this time per VOSE. For licencing purposes, a virtual core maps to a hardware thread.  When licensing individual VMs, core factors (i.e. the AMD processor 0.75 factor) do not apply.

Two examples are shown below for clarification: SQL Server core licences required for a single VOSE on a dual, four-core processor server and for two VOSEs.

SQLVirtualisationExample1

 

SQLVirtualisationExample2

 

With the SQL Server 2012 Enterprise edition (note: not Standard edition), if you licence all the physical cores on the server, you can run an unlimited number of instances of SQL Server, physically or virtually as long as the number of OSEs with SQL doesn’t exceed the number of licensed cores.  For example, a four processor server with four cores per processor provides sixteen physical cores.  If you licence all sixteen cores, you can run SQL Server in up to sixteen VOSEs (or the physical OS and 15 VOSEs), regardless of the number of virtual cores allocated to each VM.  What if you want to run more than 16 VOSEs in this case?  Well, you are permitted to assign additional core licenses to the server; this is known as licence stacking.

Here’s where Software Assurance comes into play.  Licence all the physical cores with SQL Server 2012 Enterprise Edition and software assurance and your licence rights are expanded to allow any number of instances of the software to run in any number of OSEs (physical or virtual).  This SA benefit enables customers to deploy an unlimited number of VMs to handle dynamic workloads and fully utilize hardware computing capacity.  As with most SA benefits, this licence right ends if SA coverage on the SQL core licences expires.

Licensing for maximum virtualization can be an ideal solution if you’re looking to deploy SQL Server private-cloud scenarios with high VM density, Hyper-threading is being used so you’re looking at a lot of virtual cores to licence, or you’re using dynamic provisioning and de-provisioning of VM resources and you don’t want the headache of worrying about adjusting the licence count.  As you can see in the diagram below this can be very cost-effective.

SQLVirtualisationOptions

 

We run a regular licensing spotlight call on behalf of Microsoft where we cover this and other topics in more detail.  Please join us for the next call and you can view archived calls here.


What am I getting with Office 365?



Office 365 is a brand.  But Microsoft has a challenge to overcome by using that name.  Their challenge is that the Office name is so synonymous with Word, Excel, PowerPoint and so on that customers and resellers can get confused with what Office 365 actually is.

In a nutshell Office 365 is either the Office suite of client applications (Word, etc.) or online cloud services such as Exchange, SharePoint and Lync or both of those.

Below is a table containing most of the commercial Office 365 options (aka plans) you can buy along with a summary of whether that plan includes cloud services and the Office client.  A high-level list of what’s included can be found on office.microsoft.com.

Office365matrix

 

The best place to determine the detailed feature demarcation between those plans is via the Office 365 Service Descriptions on TechNet.

O365ServiceDescription

 

Licensing is straightforward with Office 365. Whatever Office 365 plan you have, the licence is per-user. This is a big difference from on premise Office which remains per-device. If you have Exchange, Lync or SharePoint on premise you can choose to licence access to these on a per-device or per-user basis or even to mix and match but the Office 365 cloud services are only per-user.

Why is this? One of the principles of cloud computing is anywhere access and typically the user will travel more than the device. I want to access my services at home, at work, at the airport, around my mum’s house. One in five men have participated in a conference call whilst on the toilet (according to research on Wtop.com). It makes sense to licence the user because they can access from any device. I can email from any device, IM and join a video-conference from any device (that supports Lync), get to my files and sites and business intelligence in SharePoint from any device. And if the Office 365 plan includes the Office client, then that can be locally installed on up to 5 devices concurrently and these can be a mix of Windows, Mac, corporate machine or personally-owned PCs.

One other important aspect to Office 365 licensing is the concept of a USL or User Subscription licence. Most Microsoft server software requires a Client Access Licence (CAL) to enable access to the software’s features. Windows Server, Exchange Server, Lync Server and SharePoint Server all require CALs. Office 365 is no exception but we call a CAL a USL because you only subscribe to online services, they’re not perpetual unlike CALs which you don’t need to buy again every year. The monthly, per-user cost of Office 365 includes all the USLs you need however the Enterprise Office 365 plans also include an implicit CAL whereas Midsize Business and Small Business plans do not.

Why is this important? If you have a hybrid infrastructure with some on premise Exchange, Lync or SharePoint servers then your users will need CALs to access those as well as USLs to access their Office 365 services. Having implicit access rights granted within the USL means you do not need to maintain CALS for those users who are covered by an Office 365 plan (one which includes cloud services). This is detailed in the Product Use Rights document for each of the on-premises servers, an example of which is the Exchange Server 2013 Standard requirements below showing that an Office 365 E1, E3 or E4 USL is fine for access but doesn’t list Midsize or Small Business USLs.

O365ProductUseRights

 

In summary, Office 365 is a big beast which can encompass the Office client suite, cloud services or both depending on which Office 365 plan you have. Each plan differs in individual features but is broadly licensed the same way; per-user. A bonus of subscribing to the Enterprise plans that include cloud services is they allow the licenced user access to on premise Exchange, Lync and SharePoint servers without needing a separate CAL.