Article update: We created a new website called MSCloudlicensing to help SPLA and CSP partners understand the different program options and use rights available to them. The site is designed to be a collaborative platform, which includes a forum to ask and answer licensing questions, document library, and licensing articles. It’s more in depth than a simple blog. Check it out, it’s free! www.mscloudlicensing.com
- Document Library: Easy to read whitepapers on licensing and best practices. What really happens in an audit? How are other service providers handling CSP and Azure? AWS licensing? https://mscloudlicensing.com/document-library/
• Forum: Experts always review and answer your licensing questions. https://mscloudlicensing.com/forum/
• Articles: Most of the splalicensing.com articles you are used to reading and many more on CSP, Azure, AWS, and other cloud providers.
Here’s a brief rundown with SQL Developer edition and what to be aware of if you decide to deploy it.
- It’s free – you can download it for zero costs
- It’s a compliance nightmare – When you deploy MAP tool in an audit, the scan typically will reveal a SQL Enterprise installation not SQL Developer edition. Most features of Developer are found in Enterprise which brings on more confusion. If you are audited, you must prove this license is for non-production environments. Which brings us to the next bullet point.
- What is a non production environment? Any time you host Microsoft software it is defined as “production.” Whether or not you charge for this access is irrelevant. (Microsoft doesn’t care if you make money off of it). If you do internal development, that’s non production. If you host a dev environment for the benefit of your customer, now that is software as a service and would be considered production.
- Microsoft made SQL Development free in 2016. For those that need prior versions, you would need to access them through Visual Studio subscriptions. Again, for non-production environments. Otherwise, you can report Visual Studio through SPLA; per user, per month.
- To play it safe, isolate the hardware for any customer’s that want to transfer their free version of SQL Dev to your datacenter environment.
One might ask if it’s free, what’s the penalty if I am found out of compliant? If you were deploying SQL Dev for production use and Microsoft finds out, you would have to true up using SQL Enterprise. In other words, if you installed SQL Dev in 2014, get audited in 2017, Microsoft could force you to true up SQL Enterprise dating back to when you first installed Developer edition. That’s not a very cheap solution!
Is this confusing? Yes. You have to make a decision of whether or not this is production or non-production environment. Do not install SQL Developer because it’s free. It may cost you in the long run.
Thank you for reading,
May 7, 2018 at 12:23 pm
I have to disagree with your 2nd point: “It’s a compliance nightmare – When you deploy MAP tool in an audit, the scan typically will reveal a SQL Enterprise installation not SQL Developer edition.” This is incorrect. MAP tool accurately queries the Edition string in the windows registry to identify the correct edition being Developer and not Enterprise.
May 9, 2018 at 8:55 pm
Fair enough. Although I politely disagree that map tool does anything accurately 😀
October 13, 2021 at 2:05 pm
Hello. I have a dout. If within a Host there is a VM with SQL Server Enterprise, I most to report the Host with SQL Server Enterprise License or only the VM?
October 13, 2021 at 3:01 pm
You license the SQL Enterpsie license if it is installed on a VM
May 23, 2022 at 3:34 am
>> If you host a dev environment for the benefit of your customer, now that is software as a service and would be considered production.
and what with platform as a service? If I sell two virtual machines: prod and dev (prod with SQL Std and dev with SQL dev) – is it correct in your opinion?
May 26, 2022 at 11:00 am
No, its benefiting your customer