Microsoft sql server 2000 product life cycle

There is also an inherent risk of running into issues during an in-place upgrade process. There is added risk during the OS upgrade process, so doing a side-by-side migration may be the more prudent, yet more costly, approach.

The following image provides an example of innovation over the various versions of SQL Server throughout the years:. If you're not ready to upgrade, and you're not ready to move to the cloud, you have the ability to purchase an Extended Security Updates subscription to receive Critical security updates for up to three years past the end of the support date.

This is best for migrations and applications requiring OS-level access. SQL Server virtual machines are lift-and-shift ready for existing applications that require fast migration to the cloud with minimal or no changes.

If you want to offload maintenance, reduce costs, and eliminate the need to upgrade in the future, you can move your workload to Azure SQL Database single database.

This option is best for modern cloud applications that want to use the latest stable SQL Server Database Engine features and have time constraints in development and marketing. If you'd like to take advantage of offloading maintenance and cost, but find the feature set of an Azure SQL Database single database too limiting, you can move to SQL Managed Instance.

A managed instance closely resembles an on-premises SQL Server, without having to worry about such things as hardware failure, or patching. Managed Instance is a collection of system and user databases with a shared set of resources that is lift-and-shift ready, and can be used for most migrations to the cloud.

This option is best for new applications or existing on-premises applications that want to use the latest stable SQL Server Database Engine features and that are migrated to the cloud with minimal changes.

Consider Azure Cosmos DB for modern, scalable, mobile, and web applications that use JSON data and require a combination of robust querying and transactional data processing. For more info, see Cosmos DB. For info about importing data, see Import data to Cosmos DB. Consider Azure table storage to store petabytes of semi-structured data in a cost-effective solution.

For more info, see Table Storage. The following table provides an approximation of lifecycle dates for SQL Server products. For greater details and accuracy, see the Microsoft Lifecycle Policy page.

If any discrepancy exists between this table, and the Microsoft Lifecycle page, then the Microsoft Lifecycle supersedes this table, as this table is meant to be used as an approximate reference. Skip to main content. This browser is no longer supported. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Microsoft Lifecycle Policy Consistent and predictable guidelines for the availability of support throughout the life of a product.

Search by Product Find Lifecycle Policy information about a product. Modern Policy Products with continuous support and servicing. Fixed Policy Products with defined end-of-support dates at the time of release. Announcements Office and Skype for Business end of support on April 11, Windows 10, version end of servicing all editions.