RSS

SQL Developer Edition: Be very…very…careful

22 Jan

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 

 

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,

SPLA Man

Advertisements
 

Tags: , , , , ,

2 responses to “SQL Developer Edition: Be very…very…careful

  1. Scott Taillefer

    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.

     
    • MS Licensing

      May 9, 2018 at 8:55 pm

      Fair enough. Although I politely disagree that map tool does anything accurately 😀

       

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s

 
%d bloggers like this: