Migrating from SQL Server 2005

SQL Server 2005 reaches the end of Extended support in Apr. 2016 and organizations should be planning migration now to mitigate future security risks. Robust backward compatibility features and migration tools enable a range of migration options and destinations, including attaching existing databases to newer SQL Server versions, complete upgrades of the server software and databases, and new hosted solutions, including Azure. However, SQL Server includes many components, such as services, disaster recovery, management tools, and applications that are likely to complicate a migration.

Risk and Mitigation

The risks and costs of running SQL Server 2005 will rise with the end of Extended support; therefore, organizations should respond by upgrading systems and migrating databases and services to newer on-premises versions or hosted services.

End of Support Raises Risks

Once a software version exits Extended support, Microsoft will not release patches for security vulnerabilities or other bugs in the version without a costly additional custom support agreement. This means that systems running the version will become increasingly vulnerable to attack. SQL Server 2005 has continued to receive security patches over the last year, so there are likely vulnerabilities yet to be discovered and exploited by attackers if left unpatched. Unpatched systems could also exhibit new bugs and compatibility problems as an organization updates configurations and applications, which could jeopardize the ability to continue to run the organization’s applications on the database engine.