Have you ever encountered strange error messages while working with SQL Server? One developer recently reached out to me with a query about an expiration date he noticed after installing SQL Server 2016 Developer Edition from MSDN. He was confused and wanted to know the reason behind it.

Let’s take a closer look at the issue he faced. The developer ran the following query:

SELECT create_date AS 'SQL Server Installation Date',
	   DATEADD(dd, 180, create_date) AS 'SQL Instance will Stop Working ON'
FROM sys.server_principals
WHERE NAME = 'NT AUTHORITY\SYSTEM'
	

Upon running this query, he noticed an expiration date. However, it’s important to note that this query is only applicable if you are running an Enterprise Evaluation Edition of SQL Server.

Here’s an updated version of the query that takes into account different editions:

DECLARE @edition SQL_VARIANT
SELECT @edition = SERVERPROPERTY('Edition')

IF (@edition = 'Enterprise Evaluation Edition' OR @edition = 'Enterprise Evaluation Edition (64-bit)')
BEGIN
	SELECT create_date AS 'SQL Server Installation Date',
		   DATEADD(dd, 180, create_date) AS 'SQL Instance will expire on'
	FROM sys.server_principals
	WHERE NAME = 'NT AUTHORITY\SYSTEM'
END
ELSE
BEGIN
	PRINT 'You are running ' + CONVERT(VARCHAR(100), SERVERPROPERTY('Edition')) + ' which won''t expire'
END
	

By running this updated query, you will get the correct information about the expiration date if you are using the Enterprise Evaluation Edition. For other editions, you will receive a message stating that the edition does not expire.

It’s important to be aware of the edition you are installing on your servers to avoid any unexpected expiration dates. If you mistakenly install the wrong edition, you may encounter limitations or restrictions that can impact your work.

Remember, the Developer Edition of SQL Server does not require activation and never expires. The expiration date query is only applicable to the Enterprise Evaluation Edition.

Have you ever faced similar situations? Did you accidentally install the wrong edition on your servers? It’s always a good idea to double-check the edition you are installing to ensure it aligns with your requirements.

Let me know if you have any questions or if you’ve encountered any other interesting scenarios while working with SQL Server. It’s always a great learning experience to explore different aspects of this powerful database management system.

Summary: You do not have to activate the Developer Edition of SQL Server, and it never expires. The expiration date query is not applicable to any edition other than the Enterprise Evaluation Edition.