The Azure Hybrid Benefit for SQL Server allows you to choose where you use a SQL Server licence: either on-premises or in Azure. Not only that, you’re allowed to choose between an Azure virtual machine (IaaS) or the Azure SQL Database service (PaaS). This article is useful if you’re interested in an overview of the business motivations for choosing one Azure option over another: http://bit.ly/SQLOptions. Customers are eligible for the Azure Hybrid Benefit by having active Software Assurance on their licences or buying a Server Subscription.
Microsoft announce Extended Security Updates for Windows Server and SQL Server 2008/2008 R2. These products go out of extended support in the near future: 9 July 2019 for SQL Server, and 14 January 2020 for Windows Server. Extended Security Updates give three more years of support and, if the workloads are moved to Azure, then there’s no charge. Customers with Enterprise Agreements may purchase Extended Security Updates for their remaining on-premises deployments, if required. Find the announcement here: http://bit.ly/2uAxwmw and a Datasheet and an FAQ here: http://bit.ly/MSLicensingGuides.
Microsoft announce the preview of Azure SQL Database Managed Instance, a new deployment option in SQL Database that streamlines the migration of SQL Server workloads to a fully managed database service in Azure. Interesting from a licensing perspective is that you can use your SQL Server licences with SA to pay a reduced rate on a Managed Instance via the new Azure Hybrid Benefit for SQL Server.
Managed Instances are available in 8, 16, or 24 core flavours and existing on-premises Core licenses with SA can be allocated to these instances to pay the aforementioned reduced rate. SQL Server Standard Core licences cover one virtual core, and SQL Server Enterprise Core licences cover four virtual cores.
So, let’s take a look at The Papaya Hire Company’s existing SQL Server licences to see what SQL Database Managed Instances they could license. They have 16 Standard licences and 8 Enterprise licences – all with SA of course. If we work out the number of virtual cores these licences will cover we get (16 x 1) + (8 x 4) = 48 virtual cores. This means they could choose 6 x 8-core instances, or 3 x 16-core instances, or 2 x 24-core instances, or any combination of those.
If you don’t fancy doing the calculations yourself then you can use the Azure Hybrid Benefit Savings Calculator to do the mathematical heavy lifting. Find that calculator here: http://bit.ly/2pB61XH and don’t forget the usual Azure Pricing Calculator which will allow you to compare pricing for Azure SQL Database Manged Instances with and without applying the Azure Hybrid Benefit: http://bit.ly/AzurePricingCalculator. The Microsoft announcement is also useful for an overview of the features and the licensing and you can find that here: http://bit.ly/2u9SQ4D. If you’re interested in the documentation around the Azure Hybrid Benefit for SQL Server then refer to page 51 of the March 2018 Product Terms document.
We’ve just updated our Licensing Guides Emporium with a SQL Server 2017 Licensing Guide. It’s got all the information you’d expect, and a useful section on licensing SQL Server in containers. Find it here: http://bit.ly/MSLicensingGuides.
There’s a brand new SQL Server 2017 Licensing Datasheet to support general availability of this product on 2nd October 2017. There aren’t changes to the fundamental licensing but this datasheet is a nice summary including useful information such as the differences in SA benefits between Standard and Enterprise editions.
Find it in the Application Servers section here: http://bit.ly/MSLicensingGuides.
Microsoft announce that SQL Server 2017 will be generally available on 2nd October 2017. The blog post announcement is here: http://bit.ly/2xDEo4E and gives you some detail on the (actually quite exciting) new features that will be part of SQL Server 2017.
However, if you’re more interested in a summary, here are the top three things to know from a licensing perspective:
- A new “Azure Hybrid Benefit for SQL Server” allows customers to re-use existing on-premises SQL Server licences to run database-as-a-service in Azure
- R Server is renamed “Machine Learning Server for Hadoop” and is now available to all SQL Server Enterprise edition customers as an SA benefit
- It’s the first version of SQL Server to run on Windows Server, Linux and Docker, and there’s a new “SQL Server on Red Hat Enterprise Linux offer” which gives discounts off both SQL Server 2017 and the operating system to help with migrations
Microsoft announce that the next version of SQL Server will be SQL Server 2017. It’s currently at the Community Technology Preview stage and when released will be available on Windows, Linux and Docker. Find the announcement here: http://bit.ly/2pVaZiQ.
Microsoft announce Premium Assurance on 8 December 2016 (http://bit.ly/2hxi0ix) which is a way of adding six more years of product support for either Windows Server or SQL Server.
There’s a useful datasheet which gives more details, but here are the highlights: you need SA to be able to purchase Premium Assurance, and you must purchase it for ALL servers with active SA in an EA, EES or SCE. You also need to acquire Premium Assurance for a product before it goes out of support, and the price will go up over the next few years – from March 2017 it will be 5% of the licence cost rising to 12% from July 2019.
You can find the datasheet in the Core Infrastructure section in our Licensing Guides emporium: http://bit.ly/MSLicensingGuides.
If you want an overview of the different ways that you can run SQL Server on Azure virtual machines, and how they’re licensed, then this Microsoft FAQ page is worth a read through: http://bit.ly/28TwWoH.
There’s an updated (June 2016) “Licensing Microsoft server products for use in virtual environments” Volume Licensing Brief.
It’s updated for Exchange Server 2016 (no changes to the licensing), SQL Server 2016 (Business Intelligence edition removed, requirement to assign a minimum of 4 licences per processor rather than using the Core Factor table) and it references the Product Terms document rather than the Product List and Product Use Rights documents.
Get this updated brief here in the Application Servers section: http://bit.ly/MSLicensingGuides.