<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>sql-server on Code it Yourself</title><link>https://carlos.mendible.com/tags/sql-server/</link><description>Recent content in sql-server on Code it Yourself</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Carlos Mendible</copyright><lastBuildDate>Thu, 23 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://carlos.mendible.com/tags/sql-server/index.xml" rel="self" type="application/rss+xml"/><item><title>Identify SQL Server EOL &amp; ESU Costs with azqr</title><link>https://carlos.mendible.com/2026/07/23/identify-sql-server-eol-esu-costs-with-azqr/</link><pubDate>Thu, 23 Jul 2026 00:00:00 +0000</pubDate><guid>https://carlos.mendible.com/2026/07/23/identify-sql-server-eol-esu-costs-with-azqr/</guid><description>&lt;p>Running SQL Server past its end-of-life date exposes your organization to &lt;strong>unpatched security vulnerabilities and growing Extended Security Update (ESU) costs&lt;/strong>. Understanding exactly which instances are affected — and what it could cost you — is the first step toward a sound modernization strategy.&lt;/p>
&lt;p>This post introduces the &lt;a href="https://github.com/azure/azqr" target="_blank" rel="noreferrer">Azure Quick Review&lt;/a> &lt;code>sql-esu&lt;/code> plugin, which scans both Arc-enabled SQL Servers and Azure SQL VMs, estimates your possible ESU spend, and recommends migration paths to Azure SQL Managed Instance (SQL MI).&lt;/p></description></item></channel></rss>