2. Can I Extend the Life of SQL Server?
For legacy applications that are running well and that don’t require change, keeping old versions of Windows Server and SQL Server around beyond year 13 is a fairly low-risk approach. It’s best, however, to move everything possible off that server, such as other applications or any databases that could be migrated to a newer version.
3. What Issues Might Cause Problems with Old SQL Server Versions?
Most important is capacity limits; databases tend to grow, and if an agency hits the wall on database size, number of records or even disk space, that can be a hard stop. Poor performance is also something that can creep up on IT managers. Everything may work well until resources run out of memory or CPU capacity. Keeping an eye on SQL and Windows limits, issues with Active Directory versions and overall resource consumption is important when extending the life beyond Microsoft’s recommendations.
DISCOVER: How modern data platforms deliver efficient government services.
4. What’s the Best Approach Adopting a Newer Version?
In a world of virtual machines, the best approach is to spin up a new version of SQL Server on the latest version of Windows Server and migrate applications and data. This lets administrators fall back easily and offers the least risk during the migration. Managers will have to move all that data from the old database to the new one, which will take time and create a crimp in production, but it’s only done once or twice a decade.
5. When Should I Consider Other Platforms?
Consider a non-Windows platform only if an agency has very specific requirements that force an alternative path. SQL Server will always be harder to support and will lose some features when running on non-Windows platforms. If SQL Server is required, stick with Windows Server as the underlying platform if possible.
