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,