web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Upgrade of SQL 2016 ev...
Finance | Project Operations, Human Resources, ...
Unanswered

Upgrade of SQL 2016 evaluation version to SQL 2016 standard runtime edition

(0) ShareShare
ReportReport
Posted on by Shirley McCutcheon 163

I have a client who upgraded a few months ago to GP 2018.   Their IT guy had installed a new version of SQL Server 2016 prior to the upgrade.   They now have a new IT person and he has discovered that the version of SQL 2016 is an evaluation version.  They would like to order and use the runtime edition of SQL 2016.   Will it work OK to run the edition upgrade from the SQL Server Installation Center and put in the runtime reg keys for SQL 2016 Standard runtime to get them on a version that is not an evaluation version?

One odd thing that we have noticed is that it has been more than 6 months since the upgrade but the evaluation version of SQL is still running without issue.  Thanks for any assistance.

Categories:
Microsoft Dynamics GP
I have the same question (0)
  • Richard Wheeler Profile Picture
    Richard Wheeler 75,848 Moderator on at
    RE: Upgrade of SQL 2016 evaluation version to SQL 2016 standard runtime edition

    Perhaps this article will help.

    https://www.sqlservercentral.com/blogs/upgrade-sql-server-evaluation-edition-to-license-edition-of-sql-server

  • Shirley McCutcheon Profile Picture
    Shirley McCutcheon 163 on at
    RE: Upgrade of SQL 2016 evaluation version to SQL 2016 standard runtime edition

    I have read articles on how to enter SQL registration keys to make SQL a registered copy using the method described here, but my concern was whether it would be any different using the runtime version of the software.  I was also wondering whether it would be best to run the Edition Upgrade from the existing installed software or should I run it from the SQL runtime disk - or does it make any difference.?

    Thank you for the quick reply!

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,848 Moderator on at
    RE: Upgrade of SQL 2016 evaluation version to SQL 2016 standard runtime edition

    SQL runtime is more of a legal term than a difference. With GP YOU SHOULD only use it with GP related databases. The evaluation license is another matter. If it is not too much of a bother I would uninstall the evaluation version and install the runtime version. This would load SQL with the proper product ID. Follow the steps in KB878449.

  • Shirley McCutcheon Profile Picture
    Shirley McCutcheon 163 on at
    RE: Upgrade of SQL 2016 evaluation version to SQL 2016 standard runtime edition

    Please explain what you mean by "The evaluation license is another matter".   If it is an evaluation version there would be no license entered.   The main issue with creating a new install is just transferring Management Reporter.

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,848 Moderator on at
    RE: Upgrade of SQL 2016 evaluation version to SQL 2016 standard runtime edition

    You should not be using an evaluation license for production. Functionally it will work but any audit will catch that and require a full license.

  • Shirley McCutcheon Profile Picture
    Shirley McCutcheon 163 on at
    RE: Upgrade of SQL 2016 evaluation version to SQL 2016 standard runtime edition

    Of course.   The former IT person must have just forgotten and he left soon after that.  I suppose the main question is whether the runtime version is actually a different product ID or is it just a matter of changing a license key.  Thank you!

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,848 Moderator on at
    RE: Upgrade of SQL 2016 evaluation version to SQL 2016 standard runtime edition

    The runtime SQL is gotten off of CustomerSource.  When you install it you will see the product ID. I have never installed an evaluation copy so I do not know if the same thing happens. I would assume the evaluation copy is time bombed so one day it will just stop working. You will eventually see something like this.

    support.microsoft.com/.../evaluation-period-has-expired-error-message-when-working-with-sql-serv

  • Shirley McCutcheon Profile Picture
    Shirley McCutcheon 163 on at
    RE: Upgrade of SQL 2016 evaluation version to SQL 2016 standard runtime edition

    Yes, I have installed the runtime version many times.   When you install it, it shows the reg keys but that field is not accessible.  You do need to write those keys down so that if you install SSRS you will have them to enter on that installation.  I have the runtime on my laptop and when I run @@Version it gives this.

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Microsoft SQL Server 2016 (SP1-GDR) (KB4505219) - 13.0.4259.0 (X64)

    Jun 15 2019 19:20:12

    Copyright (c) Microsoft Corporation

    Standard Edition (64-bit) on Windows 10 Pro 6.3 <X64> (Build 18362: ) (Hypervisor)

    It doesn't say anything about it being a runtime version, just a standard version.

    When you install a version of regular SQL standard and don't enter a reg key it is automatically an evaluation version.

    Thanks for your help!

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,848 Moderator on at
    RE: Upgrade of SQL 2016 evaluation version to SQL 2016 standard runtime edition

    Mine makes no mention of runtime either. Which is why I think the runtime name is just a legal term.

    Microsoft SQL Server 2019 (RTM-GDR) (KB4517790) - 15.0.2070.41 (X64)   Oct 28 2019 19:56:59  

    Copyright (C) 2019 Microsoft Corporation  Standard Edition (64-bit) on Windows 10 Pro 10.0 <X64> (Build 19041: ) (Hypervisor)

    What does this tell you? Evaluation copies expire 180 days after installation date.

    SELECT

    @@SERVERNAME as SERVERNAME,

    create_date as 'INSTALLATIONDATE',

    SERVERPROPERTY('EDITION') as 'Version',

    DATEADD(DD, 180, CREATE_DATE) AS 'EXPIRY DATE'

    FROM SYS.SERVER_PRINCIPALS

    WHERE SID = 0X010100000000000512000000

  • Shirley McCutcheon Profile Picture
    Shirley McCutcheon 163 on at
    RE: Upgrade of SQL 2016 evaluation version to SQL 2016 standard runtime edition

    I don't have access currently to their server to run that.   But we know for a fact that it has been running longer than 180 days.   But we know for a fact that it has been longer than 6 months, but it is still running without issue.   That is the weird thing.   We may just go ahead and call Microsoft to get their opinion or just install SQL 2017 runtime on the same server and move to that.  Thanks!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
CA Neeraj Kumar Profile Picture

CA Neeraj Kumar 1,964

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 823 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 564 User Group Leader

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans