SQL Server Developer edition risks

Question

SQL Server Developer edition risks

csales

Ten Centuries

Points: 1219
More actions
July 18, 2018 at 5:55 am

#354696

Hi there,
We're currently reviewing our SQL Server licensing within our non-production environments. The majority of our production environments run SQL Server Standard edition 2016.
I'm interested in understanding the risks of running SQL Server 2016 developer edition across our non-production environments. The most obvious one is that the Developer edition has Enterprise features which obviously won't work when we move between non-prod and prod. I'm less nervous about this as I feel we can manage this risk. What would be a concern however is if the underlying database engine between Developer and Standard edition were different.
Can anyone offer an opinion as to whether there are real risks, and/or whether these can be mitigated? I'd also be interested in how patching Developer vs Standard editions work. eg are the binaries/packages different or the same.
Any advice appreciated.
thanks.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

alex.sqldba SSChampion Points: 10254 More actions · Answer 1

Hi.

This won't answer your specific question about the binaries, but in terms of managing risk of feature-overuse, the following query might help:
SELECT * FROM sys.dm_db_persisted_sku_features
You could even schedule it run on your Development server a few times a day and send an email alert if any Enterprise features are found to be in use.

jasona.work SSC Guru Points: 50117 More actions · Answer 2

Really you are correct, your biggest concern is just going to be making sure that the developers don't use any Enterprise edition-only features. As far as patching, the engine, etc, there is no difference. You'll download the same Service Pack / Cumulative Update files for both (arguably, for any edition from Express up through Enterprise)

csales Ten Centuries Points: 1219 More actions · Answer 3

jasona.work - Wednesday, July 18, 2018 6:46 AM
Really you are correct, your biggest concern is just going to be making sure that the developers don't use any Enterprise edition-only features. As far as patching, the engine, etc, there is no difference. You'll download the same Service Pack / Cumulative Update files for both (arguably, for any edition from Express up through Enterprise)

Hi,
So are you saying the binaries/code base between Dev/Std/Ent versions are all the same and that the different versions are "enabled" via config or flags?
thanks.

jasona.work SSC Guru Points: 50117 More actions · Answer 4

csales - Wednesday, July 18, 2018 7:34 AM
jasona.work - Wednesday, July 18, 2018 6:46 AM
Really you are correct, your biggest concern is just going to be making sure that the developers don't use any Enterprise edition-only features. As far as patching, the engine, etc, there is no difference. You'll download the same Service Pack / Cumulative Update files for both (arguably, for any edition from Express up through Enterprise)
Hi,
So are you saying the binaries/code base between Dev/Std/Ent versions are all the same and that the different versions are "enabled" via config or flags?
thanks.

I don't know how, exactly, MS handles enabling / disabling the various features between versions. But the underlying code base is essentially the same. If you have the same database, with the same data, on SQL Express, Standard, and Enterprise, all three will return the same results, with the same query plan (well, Express might end up with a different plan, due to processor count limits.)

So, again, based on your original question, the only thing to really worry about is making sure your devs don't take a shine to an Enterprise feature...

Chris Harshman SSC-Forever Points: 42192 More actions · Answer 5

One thing I recall, although I don't use the feature very often, is that in Standard edition you would have to use the NOEXPAND hint when querying an indexed view, in Enterprise / Developer editions it wasn't needed.

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 6

Chris Harshman - Wednesday, July 18, 2018 10:46 AM
One thing I recall, although I don't use the feature very often, is that in Standard edition you would have to use the NOEXPAND hint when querying an indexed view, in Enterprise / Developer editions it wasn't needed.

I recall that as, but it has been a while since I had to use it.