SQL Server 2016 EOS 目前 ― Azure Arc で棚卸し・保護・ESU 延命・移行評価までを実機で確認する As SQL Server 2016 nears End of Support, this article demonstrates how Azure Arc enables i…

SQL Server 2016 reaches the end of its extended support lifecycle on July 14, 2026, and organizations still running the release face a familiar deadline: after that date, Microsoft stops shipping regular security updates for the product. This article walks through how Azure Arc can serve as a single control plane for the practical tasks that milestone demands—taking inventory of every instance, hardening security, extending the supported lifetime through Extended Security Updates (ESU), and assessing readiness for migration—verified in a hands-on environment rather than described in the abstract.

The immediate concern with any end-of-support (EOS) database is not that it stops working. SQL Server 2016 will continue to run after July 2026. The risk is that newly discovered vulnerabilities will no longer be patched, which raises exposure and can create compliance gaps for regulated workloads. Because many production estates contain instances installed years ago and only loosely tracked, the first problem is often simply knowing what exists and where.

Azure Arc addresses that discovery problem directly. Azure Arc-enabled SQL Server installs a lightweight extension on the host through the Connected Machine agent, then reports each detected instance and database up to Azure. Once connected, servers appear as first-class resources in the Azure portal alongside native cloud databases, giving administrators a consolidated inventory with edition, version, patch level, and configuration details. This inventory is the prerequisite for everything that follows: you cannot protect, license, or migrate instances you have not enumerated.

For security, Azure Arc connects on-premises SQL Server to cloud tooling that would otherwise be unavailable. Microsoft Defender for Cloud can extend its SQL protections—vulnerability assessment and behavioral threat detection—to Arc-enabled instances, and the built-in best practices assessment flags configuration weaknesses against Microsoft guidance. These capabilities do not replace security patches, but they help reduce the attack surface during the window when an unpatched engine remains in service.

ESU is the mechanism that keeps that window supported. Extended Security Updates provide critical security fixes for up to three years after the EOS date for customers who need more time. Historically, ESU required volume licensing agreements and upfront purchase. Through Azure Arc, Microsoft now offers ESU for on-premises SQL Server on a pay-as-you-go basis, billed monthly per core through an Azure subscription, with updates delivered to enrolled Arc-connected instances. Notably, workloads already running in Azure—on Azure SQL Managed Instance or SQL Server on Azure Virtual Machines—receive ESUs at no additional charge, which is part of the incentive structure Microsoft has built around migration.

That leads to the final stage: migration assessment. Rather than treating ESU as a permanent solution, the recommended path is to evaluate targets such as Azure SQL Managed Instance, Azure SQL Database, or a supported newer SQL Server version. Azure Arc, together with the broader Azure Migrate and Data Migration Assistant tooling, can assess feature compatibility, surface deprecated features and breaking changes, and estimate sizing for cloud targets. The Azure SQL Migration extension for Azure Data Studio supports both the assessment and the migration itself.

For teams planning this work, a few prerequisites are worth confirming. The Connected Machine agent needs outbound connectivity to Azure endpoints, appropriate Azure role-based access control assignments, and the relevant resource providers registered in the target subscription. ESU billing through Arc requires the license resource to be configured correctly to avoid unexpected charges, so validating the setup in a test environment first is prudent. Organizations that handled prior transitions, such as the SQL Server 2012 and Windows Server 2012 end-of-support events, will recognize the pattern, and Azure Arc consolidates steps that previously spanned several disconnected tools.

The broader takeaway is that Azure Arc reframes an EOS deadline from a one-off scramble into a repeatable governance workflow. Even for organizations that ultimately intend to remain on-premises, the inventory and assessment data it produces is valuable, and the same approach appears applicable to the coming end-of-support dates for other SQL Server and Windows Server versions. Treating the 2016 deadline as a rehearsal for those later milestones is likely the more durable strategy, since the underlying tasks—discover, protect, extend, and assess—recur with each lifecycle transition.