Licensing SQL Server has always been a bit of a pain point. Luckily, Microsoft hasn’t really changed anything in eight years. If you could license SQL 2012, 2014, or 2016,…
Read More
UPDATE: We have changed the color codings to reflect what’s overdue and what’s upcoming in terms of support expirations. Additionally, we’ve updated it to include the changes to the Semi-Annual…
The big push and talk at Ignite this year was all about Azure, Office 365, AI and the combination thereof. In fact, it was discussed so heavily that it can…
(This post is an update to “Do I Need SQL CALs When Using SharePoint?” first posted on the Mirazon blog on September 3, 2013.) When you advise people on Microsoft licensing…
In my last post, I discussed the basics of SQL licensing. In this post, I will answer the question: How do you properly license SQL Server 2016 in a virtual environment?…
As of June 1, 2016, Microsoft SQL Server 2016 is available for purchase. In May, I published a preliminary report on SQL 2016 licensing. As promised, here is my full…
On May 2, Microsoft announced that SQL Server 2016 will be generally available on June 1, 2016. Here’s what we know and don’t know yet, as far as licensing goes….
Microsoft is making a version of SQL for Linux. No, you’re not asleep. No, this isn’t the Twilight Zone … it’s real. “Why?” you ask? There are several very good…
Microsoft has made it crystal clear that “Extended support for SQL Server 2005 ends on April 12, 2016.” What exactly does that mean? No more security updates. No more feature…
In our last few posts, we have covered the basics of SQL licensing, the breaking points between the main versions, and the use right changes made when SQL 2014 was…
In our last two posts, we have covered the basics of SQL Server licensing and we have examined the breaking points between some of the key versions of the product….
In my last post, I covered the basics of SQL Server 2014 licensing. We discussed the three main versions: Enterprise, Business Intelligence (BI), and Standard. We also covered the “Per Instance”…