SQLskills has an ongoing initiative to blog about basic topics, which we\u2019re calling SQL101. We\u2019re all blogging about things that we often see done incorrectly, technologies used the wrong way, or where there are many misunderstandings that lead to serious problems. If you want to find all of our SQLskills SQL101<\/strong> blog posts, check out <\/font>SQLskills.com\/help\/SQL101<\/font><\/a>.<\/font><\/p>\n A relatively common task that you may have to handle as a database professional is upgrading to a different edition of SQL Server on an existing instance of SQL Server. This is known as an Edition Upgrade, and Microsoft documents the procedure here<\/a>. This is different than a version upgrade (such as going from SQL Server 2012 to SQL Server 2017).<\/font><\/p>\n The two most common scenarios are upgrading from Evaluation Edition to a paid Edition, and upgrading from Standard Edition to Enterprise Edition. There are other possible paths, that are listed for SQL Server 2016<\/a> and for SQL Server 2017<\/a>.<\/font><\/p>\n In order to upgrade the Edition of SQL Server, you will need your SQL Server installation media (which is typically an .iso file). With modern versions of Windows Server you can right-click on the .iso file and select Mount to make the contents of the .iso file available. From the root folder, double-click setup.exe. Once the SQL Server Setup program has loaded (SQL Server Installation Center), click Maintenance, and then select Edition Upgrade. <\/font><\/p>\n After a few seconds, you should see the Product Key page as shown in Figure 1. If you are upgrading to a paid edition, you will need a Product Key that will look something like this: 7GPYM-VHN83-PHDM3-Q9T2R-KBV91 <\/font><\/p>\n Figure 1: Product Key<\/strong><\/font><\/p>\n Next, you\u2019ll have to accept the license terms, as shown in Figure 2.<\/font><\/p>\n Figure 2: License Terms<\/font><\/p>\n Next, the Edition Upgrade Rules will be checked, as you see in Figure 3.<\/font><\/p>\n Figure 3: Edition Upgrade Rules<\/strong><\/font><\/p>\n <\/p>\n Once the Edition Upgrade Rule check has completed, you can check the details as shown in Figure 4. You will have to resolve any failed rule checks before you can continue.<\/font><\/p>\n <\/p>\n Figure 4: Edition Upgrade Rules Details<\/strong><\/font><\/p>\n Next, you will have to select the instance that you want to upgrade, as shown in Figure 5.<\/font><\/p>\nIntroduction<\/font><\/font><\/h2>\n
Edition Upgrade Procedure<\/font><\/font><\/h2>\n
<\/a><\/font><\/p>\n
<\/font><\/p>\n
<\/font><\/p>\n
<\/a><\/p>\n
<\/font><\/p>\n
<\/font><\/p>\n
<\/a><\/p>\n
<\/a><\/p>\n
<\/font><\/p>\n