Blog Archive

SQL Server 2014 Licence Key

We had a question via a comment on one of our SQL Server 2014 blog posts.  It’s a little hard to answer because it lacks specific details such as part number and reseller but we like to try to answer questions.

“my company have bought 1 license sql 2014 and cd i download from website. during setup i need to insert product key. how to i get the license?”

Thanks for your query.  There are a few factors to consider which will help establish an answer:

1 – What website did you buy SQL 2014 from?  Was it a reputable reseller such as Insight or Ebuyer?  If you purchased the software through a site such as eBay, it may be that you were sold a pirated copy.
2 – What product did you buy?  Did you buy SQL Server 2014 Standard Edition Server licence or a SQL Server 2014 client access licence (CAL) or the SQL Server 2014 Developer Edition?  The price you paid (assuming it was from a legitimate reseller) will give you a clue; the standard server product with 10 CALs would be around £2,500-£3,000 whereas the developer edition would be around £50.

If you did purchase from a legitimate reseller, and was shipped a DVD in a box, then this is classed as full packaged product (FPP) and the product key to use on installation will typically be on a sticker on the DVD case.  It will be 25 alphanumeric characters in the form xxxxx-xxxxx-xxxxx-xxxxx-xxxxx.

In any case, your first port of call for help could either be the reseller you purchased this from or Microsoft support who can both advise you if the product is legal and legitimate and help you with the installation.  They can be reached on (+44) 344 800 2400.  You can also log a web support incident via Microsoft’s support page.

You can download a white paper on licensing Microsoft SQL Server or of course look into attending one of our licensing courses.


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.