I have a question about the installation of SQL Server 2016.

We Installed a trial version tha was made on 2017/09/19

According to the script that I execute in the database, the expiration date was 2018/03/18 but we can still use it without problems.

The Sharepoint site that uses this DB does not give any errors or warnings legends that it is expired or that some features are no longer available. I can also enter from MSQLServer Management Studio and execute scripts, create new DB, etc.

How can exactly know the expiration date?

WHERE SID = 0X010100000000000512000000

SERVERNAME      INSTALLATIONDATE        Version                                 EXPIRY DATE
SAHARCVSPS02    2017-09-19 13:15:20.967 Enterprise Evaluation Edition (64-bit)  2018-03-18 13:15:20.967
  • 2
    I'd be wary of continuing to run an instance you know is passed the expiration date. We had a server running an evaluation edition still worked even though it was expired, but when the server rebooted, the instance wouldn't restart and the server didn't acknowledge that SQL was ever installed on it.
    – Taryn
    Apr 9, 2018 at 14:51

3 Answers 3


SQL Server doesn't stop the service when it hits the expiration. Instead, it is checked when the service starts. If you restart the service, or reboot, or your system crashes, when it tries to come back up, it won't start.

So I'd take your backups, clean SQL Server off the machine entirely (since other components like SSMS might still give you expiration issues) and fix this - before you have to restart the service or reboot and you're not prepared.

David points out that upgrading from eval to full license is supported, but I avoid that because I’ve had more than one experience where that definitely did not go smoothly. Hopefully this isn’t production, where eval should never have been used in the first place, but in any case I think it is cleaner and safer to nuke and pace than try an in-place upgrade. Those have a variety of potential pitfalls even when an expired eval edition isn’t part of the mix.

I have a post about fully removing evaluation edition, but please don't start this process until you've validated your backups are all good and you've scripted logins, jobs, linked servers etc.

The actual date isn't important now, IMHO. If you have sour milk in the fridge, it's sour, and you should throw it away, whether it expired on Easter or on Christmas. Also note that some components may expire sooner, e.g. if you install SSMS along with one instance of eval edition, then install another instance of eval edition later, SSMS will expire with the first one, not the second.


How can exactly know the expiration date?

You've found it. It is expired, and out-of compliance. It will stop working soon.

There should be no need to wipe and reinstall SQL Server. You can perform a quick, in-place Edition Upgrade. The supported Edition Upgrade paths are listed here, and in this case are:


SQL Server 2016 (13.x) Evaluation Enterprise**


SQL Server 2016 (13.x) Enterprise (Server+CAL or Core License)

SQL Server 2016 (13.x) Standard

SQL Server 2016 (13.x) Developer

SQL Server 2016 (13.x) Web

Of course any time you are installing software on your server, you should ensure that you have a current set of backups.


The expiration date is always 180 days after installation.

You can find it in the logs. Check out MSSQLGirl - Retrieving SQL Server 2012 Evaluation Period Expiry Date

Run a query:

    create_date AS 'SQL Server Install Date',
    DATEADD(DD, 180, create_date) AS 'SQL Server Expiry Date'
FROM sys.server_principals

Check the summaryLog.txt

“C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\LOG\Summary.txt“.

Check the registry:


Please note this was based on SQL Server 2012.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.