SQL Server 2014 has officially reached its end of support, marking a critical turning point for companies looking to stay ahead. The decisions made regarding your SQL Server can be overwhelming but Interlink is here to help guide you through your options. Detailed below is a quick guide to help you and your business understand more about the risks of inaction and next steps for SQL Server 2014.
Risks associated with inaction and running outdated software:
1. Security Vulnerabilities
Without security patches, databases become targets for attacks, leading to potential data theft and severe financial and reputational damage.
2. Compliance Issues
Using unsupported software may result in non-compliance with regulatory requirements, legal penalties, and loss of customer trust.
3. Operational Failures
No support for bugs or issues can lead to system downtime, data loss, and disruption of business operations, affecting productivity and revenue.
4. Increased Costs and Technological Obsolescence
The expenses associated with maintaining outdated systems can far outweigh the costs of upgrading, considering the potential for increased downtime and security incidents. Additionally, remaining on SQL Server 2014 may limit the ability to integrate with modern applications and technologies, hindering innovation and competitive edge.
Options for Transition:
1. Upgrade to a Newer Version of SQL Server
Upgrading to a newer version of SQL Server not only provides the latest features and improved performance but also renews the support lifecycle, helping to maintain environmental consistency and access to SQL Server innovations.
2. Migrate to Azure SQL Managed Instance
Migrating to Azure SQL Managed Instance offers a fully managed PaaS solution with evergreen SQL, eliminating the need for manual patching or updates.
3. Move to Azure Virtual Machines
Moving to Azure Virtual Machines allows businesses to lift and shift their SQL Server workloads to the cloud “as-is” and receive Extended Security Updates at no additional cost.
4. Purchase Extended Security Updates (ESU)
Purchasing Extended Security Updates provides up to three years of additional critical security updates, allowing businesses more time to plan for future upgrades or migrations.
If you need to purchase ESUs while you consider a long-term solution for your infrastructure, there are two options:
The option that we think makes the most sense is to purchase ESUs through Azure Arc, where you must license the individual VM that needs the ESU but does not need to match the licensing model of the underlying SQL license, so you can pick and choose which VM’s need the ESUs. Also, since it is an Azure service, you only pay for what you need, so if you only need the ESU for a few months while you plan to either upgrade, retire, or move that VM to Azure, you can get rid of the ESU and stop getting charged for it once it's no longer needed.
The second option is to purchase a 1-year license of the ESU on an EA or CSP agreement. When purchasing the 1 Year ESU, you are paying for the full year, regardless of how long you need the ESU. Furthermore, when purchasing the 1 Year ESU, you will need to license the ESU in the same way that the underlying SQL server is licensed, whether that be the server itself or by the cores dedicated to the VM. For example, if you license SQL Enterprise and license all the physical cores on a server for unlimited VM’s, then the ESUs must be SQL Enterprise for all cores on the physical server as well…this could get costly quickly.
Regardless of your ESU purchasing model, Software Assurance or a SQL Server Subscription must be in place before you can purchase an ESU.
Whether it’s upgrading, migrating, or extending support, it's important to take the time to consider your next steps as each option offers pros and cons for continued security and innovation. Reach out to Interlink today further detail or guidance.
Looking for information on older versions such as SQL Server 2012 or Windows Server 2012? Check out our blog post for more info!
