Upgrade edition of SQL Server 2016 SP1 from Developer to Standard

  • Hi all

    Having a strange issue. We have a production server which incorrectly got installed with Developer edition. The upgrade path is supported according to this article:

    https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades

    I go through the Edition Upgrade by launching the setup.exe and going to the Maintenance tab in SQL Server Installation Center.  I choose the instance to upgrade and when I get to the Feature Rules tab, all of my rules pass except the SQL Server 2016 edition downgrade which gives me a Warning:


    Very strange as i'm not doing a downgrade? I ran SELECT * FROM sys.dm_db_persisted_sku_features and the only enterprise feature in use is Compression. This feature is supported in Standard edition in SP1 so this shouldn't be a problem but just in case, I removed compression (was only used on one table, one of Ola Hallengren's). However i am still getting the same warning.... don't know why but i don't feel confident proceeding with the upgrade (it is after all just a Warning so it should let me proceed but can't risk it falling over half way through).

    Any ideas???

    Thanks!

  • The developer edition is the same as the enterprise edition with restricted license (i.e. developer edition can't be used for production work).  You will need to do an uninstall and reinstall.

    Of course, I could be wrong if Microsoft actually made it possible to upgrade from developer edition to standard edition.

  • Hi Lynn
    What you say makes logical sense (DEV has more features than Standard) but the official Microsoft documentation says dev to standard is a valid upgrade path!

    See the section SQL Server 2016 Edition Upgrade section in this doc:
    https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades

    ??

    I will post on the MSDN forum as well - let Microsoft answer for themselves 🙂

    Thanks
    Neile

  • doodlingdba - Thursday, March 8, 2018 9:01 AM

    Hi all

    Having a strange issue. We have a production server which incorrectly got installed with Developer edition. The upgrade path is supported according to this article:

    https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades

    I go through the Edition Upgrade by launching the setup.exe and going to the Maintenance tab in SQL Server Installation Center.  I choose the instance to upgrade and when I get to the Feature Rules tab, all of my rules pass except the SQL Server 2016 edition downgrade which gives me a Warning:


    Very strange as i'm not doing a downgrade? I ran SELECT * FROM sys.dm_db_persisted_sku_features and the only enterprise feature in use is Compression. This feature is supported in Standard edition in SP1 so this shouldn't be a problem but just in case, I removed compression (was only used on one table, one of Ola Hallengren's). However i am still getting the same warning.... don't know why but i don't feel confident proceeding with the upgrade (it is after all just a Warning so it should let me proceed but can't risk it falling over half way through).

    Any ideas???

    Thanks!

    The supported path does not mention SP1 which it would specifically if supported. Have you tried uninstalling SP1 first

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • It make sense to pop up a warning window. After all, some features are supported by Develop Edition, but not by Standard Edition. I'm curious, if we can ignore the warning, and then, what will happen.

    GASQL.com - Focus on Database and Cloud

  • Thanks Perry - I will try your suggestion re uninstalling SP1 and see what happens. You would think if anything, SP1 would be required as that is when a number of features (such as compression) became available in standard edition, bringing dev and standard edition more in line. Oh well - i'll give it a go and see if the warning disappears. I'll report back...

    Alexander - i am also curious what would happen if I proceeded with the warning, but wont chance it on a production server 🙂

  • No luck Perry - stripped SP1 and I'm still getting the warning. It's a weird one...

  • According to Microsoft  you can upgrade from developer to standard.
    https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades

  • Just wanted to report back - although I get a SQL Server 2016 edition downgrade warning (treats it as a downgrade as i am going from Dev which allows all features to Standard which doesn't), if I proceed with the upgrade it all works perfectly with no issues! The warning is just that - you can proceed and there are no issues. In my case I am not using any enterprise features so wouldn't experience any issues with this. It would be interesting to know what would happen if you tried to downgrade the edition (from dev to standard) if you were using a bunch of enterprise only features. Would it even let you downgrade? Would it let you but then give you errors when trying to utilize those ent. only features??

    Thanks all!

  • doodlingdba - Tuesday, May 22, 2018 6:29 AM

    Just wanted to report back - although I get a SQL Server 2016 edition downgrade warning (treats it as a downgrade as i am going from Dev which allows all features to Standard which doesn't), if I proceed with the upgrade it all works perfectly with no issues! The warning is just that - you can proceed and there are no issues. In my case I am not using any enterprise features so wouldn't experience any issues with this. It would be interesting to know what would happen if you tried to downgrade the edition (from dev to standard) if you were using a bunch of enterprise only features. Would it even let you downgrade? Would it let you but then give you errors when trying to utilize those ent. only features??

    Thanks all!

    No.  You would have to remove the Enterprise features from any database before doing the downgrade.  Ran into this in Afghanistan because one of our production servers actually had Enterprise Edition installed and someone (not me) had decided to experiment with some Enterprise features.  This was also on SQL Server 2005 which didn't have the nice DMVs that helped identify the features in use.  Took a bit of digging to identify all the features they used.

  • On a related note to this - is there a way to restrict features in, for example the developer edition, so they match those of one of the other editions?

  • n.ryan - Friday, May 25, 2018 3:30 AM

    On a related note to this - is there a way to restrict features in, for example the developer edition, so they match those of one of the other editions?

    If you mean can you configure DE to work only like SE, no.  You just have to know not to use the EE features.

  • Lynn Pettis - Monday, May 28, 2018 9:37 PM

    n.ryan - Friday, May 25, 2018 3:30 AM

    On a related note to this - is there a way to restrict features in, for example the developer edition, so they match those of one of the other editions?

    If you mean can you configure DE to work only like SE, no.  You just have to know not to use the EE features.

    Thanks for confirming this. It was what I expected however not all (application) developers are aware of the feature differences.

Viewing 13 posts - 1 through 12 (of 12 total)

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