A man using a laptop

Remember: End of Extended Support for SQL Server 2005

1 Jun 2015 by Jessica Hall

While some things endure a long time, others grow outdated quickly — but nothing lasts forever. Smartphone apps change within months to accommodate bug fixes and more. Software can last for years, as the lifecycles of Windows XP and Microsoft® Windows Server® 2003 show.  And soon, SQL Server 2005 will retire after 10 years on April 12, 2016. In the past decade, the database industry has transformed for the better.

Improved features make applications easier to manage and scale. Plus, not getting patches for bugs or having the option to contact Microsoft after support ends can potentially cause issues.

“A year sounds like plenty of time to plan your migration, but, depending on the type of application, the migration destination, the scale of the move and resources allocated, migrations can take several months,” wrote T.K Rengarajan, the corporate vice president for data platforms at Microsoft, in a blog post.

Important Considerations

There are many factors that your organization will need to consider as you make the transition from SQL 2005 to SQL 2014 or Azure SQL Database; however, these three questions are the most critical:

  1. Do all of the applications installed on the server and utilizing SQL Server 2005 support the target version? “Ensuring that legacy applications are supported by the latest version is an extremely important first step,” states Martin Schoombee, business intelligence architect at Insight.
  2. Is the hardware and operating system (OS) compatible with SQL Server 2014 or Azure SQL Database? Review this comprehensive list for SQL Server 2014 provided by Microsoft.
  3. What risks are associated with the upgrade, and what steps do you need to take to mitigate them? “For instance, upgrading a highly available system requires additional planning to avoid downtime,” Schoombee “Similarly, certain types of SQL Server implementations, such as clusters and mirrors, require special attention when upgrading.”
  4. Did you test upgrade scenarios in non-production environments before finalizing plans and decisions? “Not only should the upgrade procedure be tested, but the applications should be submitted to a test cycle to verify that it’s completely functional,” Schoombee says.

Take Action Now

Your organization will need enough time to develop flawless migration plans. Thorough planning will help you carefully execute the migration, ensuring that all of your systems function properly after the upgrade. If this sounds like a lot, Insight can help you select, deploy and support your technology needs. Aligned with each stage are our value-added services, and software and hardware solutions that ensure success at every step — from planning, deploying and operating to refreshing and maintaining.

“With Microsoft planning to release new versions of SQL Server every two years, support for your current version will end sooner than you think,” warns Schoombee.

Plan for the Future

If you’re in the midst of migration to a more recent operating system and you’re also planning on migrating to SQL Server 2016 in the future, it’s important that you upgrade to Windows Server 2008 R2 at the very least.

Schoombee explains, “Microsoft has not yet released the details of supported operating system versions for SQL Server 2016, but it’s common that the last two OS versions will typically be supported.”

As the necessary migration is the end of an era with SQL Server 2005, it’s an opportunity to give new value to your business. Find out more about the end of support for SQL Server 2005 from our trusted partner, Microsoft.

The post Remember: End of Extended Support for SQL Server 2005 appeared first on Insight ON.