![]() ![]() Business Planning and Finance require that Microsoft offers a gating mechanism to ensure that customers that are not paying for ESUs don’t get access. Given the PII, GDPR, and other legal requirements, it is an effective cost management mechanism for us to gate access to ESUs through Azure subscriptions. While it’s understood the registration step might be seen as a friction point, we understand paying customers would be more upset if the patch they had paid for was freely available to all in the public Microsoft Download Center. See the registration details further below. ![]() ![]() To be able to access the download link from the Azure subscription, a customer will need to register the SQL Server instances for which Extended Security Updates (ESUs) were purchased. SQL Server patches don’t require an activation key to block unauthorized or unlicensed installs: as such will be using the Azure portal to distribute any future security update packages to eligible customers, because it is already gated by the customer’s Azure subscription. This is also the process that customers will need to follow for disconnected Azure Stack. SQL Server 2008/R2 running on Windows Server 2008/2008 R2 on-premisesĬustomers who purchase Extended Security Updates for on-premises use will be able to download patches from the Azure portal, and then deploy that update package to their on-premises environment such as with any other SQL Server update. If an Azure Virtual Machine is not configured to receive automatic updates, then the on-premises download option applies. SQL Server 2008/R2 running on Windows Server 2008/2008 R2 on Azure Virtual MachinesĬustomers will receive updates automatically through existing SQL Server automatic update channels. Here’s a reference.Īs a Microsoft Partner, you should incentivize customer that chooses ESUs to subscribe to patch release notifications through aka.ms/sqlreleases or work with their technical teams to be informed about the updates. Customers can choose to run a patch manually or through other automation tools like WSUS, SCCM or third party patching tools or other automation tools. This team creates the patches and upload the patch files. The Microsoft SQL Server Product Team doesn’t ship patch application software. It's important to note that ESUs will be made available as needed, only if a security issue is found with SQL Server 2008/8R2 versions and MSR deems it a Critical update. SQL Server 2008/R2 Extended Security Updatesĭefinition of critical updates through Extended Security UpdatesĪn ESU for SQL Server is essentially a GDR. Please, find below the detailed guidance of how critical updates will be delivered to customers that choose to stay in SQL Server 2008/R2 with Extended Security Updates. This option is free in Azure SQL Server 2008 VMs and paid for on-premises deployments. If after selling the value of modernizing with Azure SQL Database, Azure SQL Server 2017 & 2019 VMs and SQL Server 2017 & 2019, your customer is not ready to move from 2008, Microsoft offers the option of having three additional years of Extended Security Updates. SQL Server migrations to Azure is solely the biggest opportunity there is for our Data & AI business and the motion didn’t stop on July, 09th. The end of support for SQL Server 20 R2 that reached it's deadline on July 9th opens a great opportunity to engage with our customers to drive roader Data Estate Modernization conversations that can lead to n.ew Azure Migration and Innovation engagements. ![]()
0 Comments
Leave a Reply. |