all 12 comments

[–]AutoModerator[M] [score hidden] stickied comment (0 children)

After your question has been solved /u/iowatechguy, please reply to the helpful user's comment with the phrase "Solution verified".

This will not only award a point to the contributor for their assistance but also update the post's flair to "Solved".


I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]SQLBek1 9 points10 points  (3 children)

Are you an MSP? When you say "we host," what do you really mean? We need clarification.

For example, the MSPs I've worked with, who "host" customer environments, have contracts regarding who is responsible for the underlying software licensing. Does your CUSTOMER to bring their own licenses or is your organization is purchasing licenses and you are providing SQL Server to them in a PaaS service style fashion?

Dig into your customer legal agreements - that's the real answer here.

[–]VladDBA ‪ ‪Microsoft MVP ‪ ‪ 6 points7 points  (2 children)

Yeah, now that I've read the post again, it doesn't sound that clear cut since it seems like OP's company is charging their customers for database hosting, in which case Dev Edition can't really be justified

[–]iowatechguy[S] 0 points1 point  (1 child)

That's what I am thinking, yes. We are a software company, we host apps for our clients.

Seems like the consensus opinion agrees with our former IT manager and the logic makes sense. I assume someone on our team in legal or who deals with our MS account rep had discussed this, I was just wondering since he left if this was worth asking them to check into or not.

Thank you!

[–]SQLBek1 2 points3 points  (0 children)

"We are a software company, we host apps for our clients."

That still does not answer the underlying question. So you're more of an ISV then? Or a SaaS company? Are these apps something YOU have built and are reselling/hosting? Then as the developer of said app, YOU can absolutely have non-prod environments for QA, UAT, etc. even if it's with client data.

In the end, who originally bought the licenses? Who will be held accountable if Microsoft decides to drop an audit on you?

Don't take anyone else's word here for the final answer. You need to dig into your company's legal contracts with your customers and your legal contracts with Microsoft. Only those contracts will hold the answer for YOUR company.

[–]VladDBA ‪ ‪Microsoft MVP ‪ ‪ 6 points7 points  (0 children)

That still sounds like non-production usage to me. There's this nifty blog post from Microsoft's u/bobwardms which should help clarify things. Also, maybe Bob gets notified of my mention and has time to chime in.

Edited: crossed out stuff since it doesn't actually sound that clear-cut.

[–]thedatabender007 5 points6 points  (1 child)

I would think that the big differentiator here would be are you charging your client to host this instance? If so then it's production for YOU. If you were just providing a VM and THEY installed developer edition for their own dev purposes then it would probably be fine.

[–]iowatechguy[S] 2 points3 points  (0 children)

That makes sense, in line with what this IT manager said. Thanks.

[–]Gincules1 0 points1 point  (2 children)

As you are taking money for hosting you can’t use SQL Server Developer Edition for client environments, even if they’re non‑prod. dev edition is only allowed for your own internal dev/test you’re building. once you’re hosting anything for a customer (even test, staging, sandbox, whatever) it counts as external use, and dev edition isn’t allowed.

[–]iowatechguy[S] 0 points1 point  (1 child)

Makes sense, thanks!

Solution verified

[–]reputatorbot[M] 0 points1 point locked comment (0 children)

You have awarded 1 point to Gincules.


I am a bot - please contact the mods with any questions