Initial version and edition in our Linux SQL Server 2017

Our starting point is a SQL Server RC version, previous to RTM release. We are working specifically on a RC2 (Release Candidate 2). Our edition is Enterprise Evaluation with temporary usage restrictions.

Supported version and edition upgrades

We can find information regarding the upgrade process at Microsoft’2 website. We verify that moving from Evaluation Enterprise to Developer is supported.

Also, SQL Server 2017 release notes de indicate upgrade is supported from version CTP 2.1. That’s previous to our RC2, so all is OK for us to start the upgrade as all our configuration is inside Microsoft’s support matrixes.

Upgrade from RC2 (14.0.900.75) to RTM CU3 (14.0.3015.40)

We must start by adding a new Linux repository due to our initial installation was performed by means of using the CTP repository available at the momento of the install process. We add the CU (Cumulative Updates) repository. We could have used the GDR alternative, but it only includes base version and criticat patches. I must thank my collegue Ignacio Vizoso for showing me this point for completing this upgrade procedure.

Now we update SQL Server binary files. This process do not affect existing databases, and is also revocable because we can perform a version downgrade to the previous RPMs as per Microsoft’s doc.

Now, let’s stop the mssql-server service and perform the yum update:

Upgrade to Developer license

We want to use a free and permanente license with no usage restriction. For doing so, we stop again the mssql-server service and execute mssql-conf setup to apply the license upgrade.

Final result

Connecting to the database server, now we can see both upgrades reflected in the configuration:


%d bloggers like this: