Edition Change Check Warning

Found an interesting little issue today when trying to install Sql Server development edition (though I’m led to believe it applies to all versions).

On the configuration check screen I noticed a warning next to “Edition Change Check”, the message of which read:

To change an existing instance of Microsoft SQL Server 2005 to a difference edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.

I did a bit of investigating and it looks as though the cause here is that I already have sqlexpress installed. It looks like I installed it along with Visual Studio some time ago and forgot it was there, so the Sql installation files are assuming they’re going to be used to upgrade this installation – which it can’t do without specific instructions.

One of the potential issues here is that in order to do this, all service packs and hotfixes need to be uninstalled (something it obviously wont do without the proper permissions). What this means for us is that after we perform the upgrade, we need to reinstall all the service packs and hotfixes to ensure proper security.

The trick then is to open up a command prompt and navigate to the cd/dvd directory that contains the sql files and run this command:

setup ADDLOCAL=SQL_Engine INSTANCENAME=MSSQLSERVER UPGRADE=SQL_ENGINE SKUUPGRADE=1

If you’ve used a different instance name for your installation of the initial version you will need to use it here instead of MSSQLSERVER. MSSQLSERVER is the default name for a standard Sql Server installation, however the named instance for a standard sql express instance is SQLEXPRESS which I suspect is the most common case where the need to do this would catch us by surprise.

Note that the Edition Change Check will show as “Success” when this has been done properly. It took me a while of testing to ensure this as the property names are case sensitive and it’s easy to make a typo. Don’t continue past the configuration check until all the checks are green.

From there it should be a standard installation with no worries.

It might be useful to note that it is in fact possible to install an instance of sql server alongside sql server express if you do not wish to upgrade (or to keep the sqlexpress name). In this case it will just install as expected and you will be able to access either instance by name at leisure.

Hope this was helpful.

Advertisements

9 thoughts on “Edition Change Check Warning

  1. Thanks for the nice article. However in my experience it isn’t caused by sql server express edition installed. I didn’t have it installed on various different machines where i tested it. To my knowledge there can be lots of reasons for that and the one i found was:

    1. Trying to add/remove any sql server components on vista and windows 7 which already has SQL Server 2005 Sercvice pack 1,2 or 3 installed. Since the installed instance is latest and updated you get this message. And obviously you need to use SKUUPGRADE=1 option in command line to avoid this message. But its not a permanent solution, every time you add / remove any SQL component it will give you the same message.
    Adeel Zafar
    http://sqlplanet.blogspot.com

  2. Right now i have situation that i need to downgrade SQL Serve Enterprise edition to developer edition. After reading your article I am very comfortable now. Thanks a lot.

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 )

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s