With Extended Help for SQL Server 2008 and SQL Server 2008 R2 ending in July 2019, to be followed six months later by the finish of Extended Help for Windows Server 2008 and 2008 R2 in January 2020, the clock is ticking on creating alterations to particular legacy applications. Upgrading to the most up-to-date versions is often an solution, but Microsoft is giving an option when upgrades are not viable: Migrate the applications to the Azure cloud to get 3 additional years of no cost Extended Safety Update help.
Microsoft’s supply: “Customers who migrate workloads to Azure virtual machines will have access to Extended Safety Updates for each SQL Server and Windows Server 2008 and 2008 R2 for 3 years just after the Finish of Help deadlines, incorporated at no extra charge more than the typical VM pricing.” To help with the migration, Microsoft permits current on-premises licenses to be transferred to the Azure cloud, and also provides a 180-day transition period in the course of which a single license applies concurrently on-premises and in the cloud.
For these legacy SQL Server 2008/R2 applications that stay crucial, some kind of higher availability or disaster recovery protection will be necessary to preserve business enterprise continuity. It is probable to totally shield these legacy applications in the state-of-the-art Azure cloud, of course, but that demands understanding and effectively configuring the required provisions. And with decade-old application, having it ideal can be somewhat difficult.
This short article supplies an overview of the higher availability (HA) and disaster recovery (DR) provisions readily available for SQL Server 2008/R2 in the Azure cloud and highlights two widespread HA/DR configurations. It is essential to note that the provisions discussed right here also apply to later versions of SQL Server and Windows Server, creating them appropriate for other applications, like any legacy ones becoming upgraded. Any variations amongst the unique versions will be noted.