SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Upgrade edition of SQL Server 2016 SP1 from Developer to Standard


Upgrade edition of SQL Server 2016 SP1 from Developer to Standard

Author
Message
doodlingdba
doodlingdba
SSCrazy
SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)

Group: General Forum Members
Points: 2481 Visits: 742
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!
Lynn Pettis
Lynn Pettis
SSC Guru
SSC Guru (400K reputation)SSC Guru (400K reputation)SSC Guru (400K reputation)SSC Guru (400K reputation)SSC Guru (400K reputation)SSC Guru (400K reputation)SSC Guru (400K reputation)SSC Guru (400K reputation)

Group: General Forum Members
Points: 400964 Visits: 43365
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.

Cool
Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
doodlingdba
doodlingdba
SSCrazy
SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)

Group: General Forum Members
Points: 2481 Visits: 742
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 Smile

Thanks
Neile
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)

Group: General Forum Members
Points: 216970 Visits: 18591
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" ;-)
Alexander Zhang
Alexander Zhang
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1173 Visits: 264
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
doodlingdba
doodlingdba
SSCrazy
SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)

Group: General Forum Members
Points: 2481 Visits: 742
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 Smile
doodlingdba
doodlingdba
SSCrazy
SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)

Group: General Forum Members
Points: 2481 Visits: 742
No luck Perry - stripped SP1 and I'm still getting the warning. It's a weird one...
Alejandro Santana
Alejandro Santana
Ten Centuries
Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)

Group: General Forum Members
Points: 1036 Visits: 1140
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
doodlingdba
doodlingdba
SSCrazy
SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)

Group: General Forum Members
Points: 2481 Visits: 742
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!
Lynn Pettis
Lynn Pettis
SSC Guru
SSC Guru (400K reputation)SSC Guru (400K reputation)SSC Guru (400K reputation)SSC Guru (400K reputation)SSC Guru (400K reputation)SSC Guru (400K reputation)SSC Guru (400K reputation)SSC Guru (400K reputation)

Group: General Forum Members
Points: 400964 Visits: 43365
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.

Cool
Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum









































































































































































SQLServerCentral


Search