Published on

July 1, 2017

Common Issue with SQL Server Edition Upgrade

As a SQL Server DBA, it’s important to be knowledgeable in various areas such as performance tuning and backup/restore. However, sometimes even the most experienced DBAs can overlook simple things. In this article, we will discuss a common issue that can occur during a SQL Server edition upgrade.

Recently, one of my DBA friends encountered an issue while upgrading their SQL Server 2016 Standard Edition to the Enterprise – core based edition. Despite completing the setup process without any errors, the SQL Server edition remained at Standard Edition. When my friend reached out to me for assistance, I asked them to run a Discovery Report to gather information about the installed features.

Upon reviewing the report, it became clear that all the features were still showing as Standard edition. This prompted me to take a closer look at the setup screens. I also asked my friend to perform the edition upgrade in front of me, so I could provide a second set of eyes.

During the edition upgrade UI process, I noticed that the Product ID (PID) was already populated. As we progressed through the setup screens, I observed that the “License Terms” page displayed Standard Edition. This was a clue that led us to identify the mistake my friend had made. Instead of using the new media provided by the licensing team for the Enterprise edition, my friend had mistakenly used the old media for the Standard Edition.

Workaround / Solution

If you ever encounter a similar situation during a SQL Server edition upgrade, there are two things you can do to resolve the issue:

  1. Use the media of the new edition provided by your licensing team.
  2. Ensure that the correct PID is entered in the setup process. You can find the PID in the DefaultSetup.ini file included with the new media.

By following these steps, my friend was able to successfully upgrade to the Enterprise edition by entering the correct PID during the setup process.

It’s important to pay attention to the details during SQL Server edition upgrades to avoid encountering issues like the one discussed in this article. By using the correct media and ensuring the accurate PID is entered, you can ensure a smooth and successful edition upgrade.

Click to rate this post!
[Total: 0 Average: 0]

Let's work together

Send us a message or book free introductory meeting with us using button below.