<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Mssql on The Ginger Sysadmin Blog</title>
		<link>https://gingersysadmin.com/tags/mssql/</link>
		<description>Recent content in Mssql on The Ginger Sysadmin Blog</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 13 Jul 2026 15:03:08 -0500</lastBuildDate>
		
			<atom:link href="https://gingersysadmin.com/tags/mssql/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>License Expired SQL Server Evaluation Edition</title>
				<link>https://gingersysadmin.com/posts/license-expired-sql-server-evaluation/</link>
				<pubDate>Mon, 13 Jul 2026 15:03:08 -0500</pubDate>
				<guid>https://gingersysadmin.com/posts/license-expired-sql-server-evaluation/</guid>
				<description>&lt;h1 id=&#34;maybe-license-your-sql-servers&#34;&gt;Maybe License Your SQL Servers&lt;/h1&gt;&#xA;&lt;p&gt;If you are reading this, you are a developer who installed SQL Server Evaluation and the 180 day window expired, OR, someone setup SQL Server with Evaluation Edition, used it in production (&amp;ldquo;we will license it later&amp;rdquo;), and then some other unsuspecting admin (me) was fairly alarmed when they did a routine service restart and SQL failed to start because that production server had never been licensed. It is definitely the first one, right?&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
