01.02.2020

Sql 2017 Versions

51

Compare Enterprise, Standard, Express, and Developer SQL Server editions to find the right SQL Server 2017 edition to meet your organization's needs. SQL Server 2017 is the latest version of SQL Server. Previous is SQL Server 2016, next is SQL Server 2019 (not yet released). ★ Starting from SQL Server 2017 Service Packs will no longer be released. Only Cumulative Updates (CUs) and critical updates (GDRs) will be provided. This article lists the supported upgrade paths from these SQL Server versions, and the supported edition upgrades for SQL Server 2017 (14.x). Pre upgrade Checklist Before upgrading from one edition of SQL Server 2017 (14.x) to another, verify that the functionality you are currently using is supported in the edition to which you are moving. Compare Enterprise, Standard, Express, and Developer SQL Server editions to find the right SQL Server 2017 edition to meet your organization's needs. For editions and supported features of SQL Server on Windows, see SQL Server 2017 - Windows. Installation requirements vary based on your application needs. The different editions of SQL Server accommodate the unique performance, runtime, and price requirements of organizations and individuals. Build intelligent, mission-critical applications using a scalable, hybrid data platform for demanding workloads. Get started with a 180-day free trial of SQL Server 2017 on Windows. Take advantage of the built-in high availability, security, and intelligence of Azure SQL Database, and use the.

This article describes the updates to the SQL Server incremental servicing model (ISM) for SQL Server 2017 as they relate to the Service Pack (SP) policy. For more information about the changes to the SQL Server ISM, see An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems.

-->

APPLIES TO: SQL Server (Windows only) Azure SQL Database Azure SQL Data Warehouse Parallel Data Warehouse

You can upgrade from SQL Server 2008, SQL Server 2008 R2, SQL Server 2012 (11.x), SQL Server 2014 (12.x), and SQL Server 2016 (13.x). This article lists the supported upgrade paths from these SQL Server versions, and the supported edition upgrades for SQL Server 2017 (14.x).

Pre upgrade Checklist

  • Before upgrading from one edition of SQL Server 2017 (14.x) to another, verify that the functionality you are currently using is supported in the edition to which you are moving.

  • Before upgrading SQL Server, enable Windows Authentication for SQL Server Agent and verify the default configuration: that the SQL Server Agent service account is a member of the SQL Server sysadmin group.

  • To upgrade to SQL Server 2017 (14.x), you must be running a supported operating system. For more information, see Hardware and Software Requirements for Installing SQL Server.

  • Upgrade will be blocked if there is a pending restart.

  • Upgrade will be blocked if the Windows Installer service is not running.

Unsupported Scenarios

  • Cross-version instances of SQL Server 2017 (14.x) are not supported. Version numbers of the Database Engine, Analysis Services, and Reporting Services components must be the same in an instance of SQL Server 2017 (14.x).

  • SQL Server 2017 (14.x) is only available for 64-bit platforms. Cross-platform upgrade is not supported. You cannot upgrade a 32-bit instance of SQL Server to native 64-bit using SQL Server Setup. However, you can back up or detach databases from a 32-bit instance of SQL Server, and then restore or attach them to a new instance of SQL Server (64-bit) if the databases are not published in replication. You must re-create any logins and other user objects in master, msdb, and model system databases.

  • You cannot add new features during the upgrade of your existing instance of SQL Server. After you upgrade an instance of SQL Server to SQL Server 2017 (14.x), you can add features by using the SQL Server 2017 (14.x) Setup. For more information, see Add Features to an Instance of SQL Server (Setup).

  • Failover Clusters are not supported in WOW mode.

    Need

Upgrades from Earlier Versions to SQL Server 2017 (14.x)

SQL Server 2017 (14.x) supports upgrade from the following versions of SQL Server:

  • SQL Server 2008 SP4 or later
  • SQL Server 2008 R2 SP3 or later
  • SQL Server 2012 SP2 or later
  • SQL Server 2014 or later
  • SQL Server 2016 or later

Note

To upgrade databases on SQL Server 2005 (9.x) see Support for 2005.

The table below lists the supported upgrade scenarios from earlier versions of SQL Server to SQL Server 2017 (14.x).

Sql Server Management Studio 2017 Versions

Upgrade fromSupported upgrade path
SQL Server 2008 SP4 EnterpriseSQL Server 2017 (14.x) Enterprise
SQL Server 2008 SP4 DeveloperSQL Server 2017 (14.x) Developer
SQL Server 2008 SP4 StandardSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2008 SP4 Small BusinessSQL Server 2017 (14.x) Standard
SQL Server 2008 SP4 WebSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2008 SP4 WorkgroupSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2008 SP4 ExpressSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2017 (14.x) Express
SQL Server 2008 R2 SP3 DatacenterSQL Server 2017 (14.x) Enterprise
SQL Server 2008 R2 SP3 EnterpriseSQL Server 2017 (14.x) Enterprise
SQL Server 2008 R2 SP3 DeveloperSQL Server 2017 (14.x) Developer
SQL Server 2008 R2 SP3 Small BusinessSQL Server 2017 (14.x) Standard
SQL Server 2008 R2 SP3 StandardSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2008 R2 SP3 WebSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2008 R2 SP3 WorkgroupSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2008 R2 SP3 ExpressSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2017 (14.x) Express
SQL Server 2012 (11.x) SP2 EnterpriseSQL Server 2017 (14.x) Enterprise
SQL Server 2012 (11.x) SP2 DeveloperSQL Server 2017 (14.x) Developer
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2017 (14.x) Enterprise
SQL Server 2012 (11.x) SP2 StandardSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2012 (11.x) SP1 WebSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2012 (11.x) SP2 ExpressSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2017 (14.x) Express
SQL Server 2012 (11.x) SP2 Business IntelligenceSQL Server 2017 (14.x) Enterprise
SQL Server 2012 (11.x) SP2 EvaluationSQL Server 2017 (14.x) Evaluation
SQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2017 (14.x) Developer
SQL Server 2014 (12.x) EnterpriseSQL Server 2017 (14.x) Enterprise
SQL Server 2014 (12.x) DeveloperSQL Server 2017 (14.x) Developer
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2017 (14.x) Enterprise
SQL Server 2014 (12.x) StandardSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2014 (12.x) WebSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2014 (12.x) ExpressSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2017 (14.x) Express
SQL Server 2017 (14.x) Developer
SQL Server 2014 (12.x) Business IntelligenceSQL Server 2017 (14.x) Enterprise
SQL Server 2014 (12.x) EvaluationSQL Server 2017 (14.x) Evaluation
SQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2017 (14.x) Developer
SQL Server 2016 (13.x) EnterpriseSQL Server 2017 (14.x) Enterprise
SQL Server 2016 (13.x) DeveloperSQL Server 2017 (14.x) Developer
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2017 (14.x) Enterprise
SQL Server 2016 (13.x) StandardSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2016 (13.x) WebSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2016 (13.x) ExpressSQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2017 (14.x) Express
SQL Server 2017 (14.x) Developer
SQL Server 2016 (13.x) Business IntelligenceSQL Server 2017 (14.x) Enterprise
SQL Server 2016 (13.x) EvaluationSQL Server 2017 (14.x) Evaluation
SQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web
SQL Server 2017 (14.x) Developer
SQL Server 2017 (14.x) release candidate*SQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) DeveloperSQL Server 2017 (14.x) Enterprise

* Microsoft support to upgrade from release candidate software is specifically for customers who participated in the Technology Adoption Program (TAP).

SQL Server 2017 (14.x) Support for SQL Server 2005 (9.x)

Ms Sql Server 2017 Versions

This section discusses SQL Server 2017 (14.x) support for SQL Server 2005 (9.x). In SQL Server 2017 (14.x), you will be able to do the following:

  • Attach a SQL Server 2005 (9.x) database (mdf/ldf files) to SQL Server 2017 (14.x) instance of database engine.

  • Restore a SQL Server 2005 (9.x) database to SQL Server 2017 (14.x) instance of database engine from a backup.

  • Back up a SQL Server 2005 Analysis Services (SSAS) cube and restore it on SQL Server 2017 (14.x).

Sql 2017 Versions

When a SQL Server 2005 (9.x) database is upgraded to SQL Server 2017 (14.x), the database compatibility level will be changed from 90 to 100. (In SQL Server 2017 (14.x), valid values for the database compatibility level are 100, 110, 120, 130, and 140.) ALTER DATABASE Compatibility Level (Transact-SQL) discusses how the compatibility level change could affect SQL Server applications.

Any scenarios not specified in the list above are not supported, including but not limited to the following:

Sql 2017 Version Number

  • Installing SQL Server 2005 (9.x) and SQL Server 2017 (14.x) on same computer (side by side).

  • Using a SQL Server 2005 (9.x) instance as a member of the replication topology that involves a SQL Server 2017 (14.x) instance.

  • Configuring database mirroring between SQL Server 2017 (14.x) and SQL Server 2005 (9.x) instances.

  • Backing up the transaction log with log shipping between SQL Server 2017 (14.x) and SQL Server 2005 (9.x) instances.

  • Configuring linked servers between SQL Server 2017 (14.x) and SQL Server 2005 (9.x) instances.

  • Managing a SQL Server 2005 (9.x) instance from a SQL Server 2017 (14.x) Management Studio.

  • Attaching a SQL Server 2005 Analysis Services (SSAS) cube in SQL Server 2017 (14.x) Management Studio.

  • Connecting to SQL Server 2005 Integration Services (SSIS) from SQL Server 2017 (14.x) Management Studio.

  • Managing a SQL Server 2005 Integration Services (SSIS) service from SQL Server 2017 (14.x) Management Studio.

  • Support for SQL Server 2005 (9.x) third party custom Integration Services components, such as execute and upgrade.

SQL Server 2017 (14.x) Edition Upgrade

The following table lists the supported edition upgrade scenarios in SQL Server 2017 (14.x).

For step-by-step instructions on how to perform an edition upgrade, see Upgrade to a Different Edition of SQL Server (Setup).

Upgrade FromUpgrade To
SQL Server 2017 (14.x) Enterprise (Server+CAL and Core)**SQL Server 2017 (14.x) Enterprise
SQL Server 2017 (14.x) Evaluation Enterprise**SQL Server 2017 (14.x) Enterprise (Server+CAL or Core License)
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Developer
SQL Server 2017 (14.x) Web
Upgrading from Evaluation (a free edition) to any of the paid editions is supported for stand-alone installations, but is not supported for clustered installations.
SQL Server 2017 (14.x) Standard**SQL Server 2017 (14.x) Enterprise (Server+CAL or Core License)
SQL Server 2017 (14.x) Developer**SQL Server 2017 (14.x) Enterprise (Server+CAL or Core License)
SQL Server 2017 (14.x) Web
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) WebSQL Server 2017 (14.x) Enterprise (Server+CAL or Core License)
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Express*SQL Server 2017 (14.x) Enterprise (Server+CAL or Core License)
SQL Server 2017 (14.x) Developer
SQL Server 2017 (14.x) Standard
SQL Server 2017 (14.x) Web

Additionally you can also perform an edition upgrade between SQL Server 2017 (14.x) Enterprise (Server+CAL license) and SQL Server 2017 (14.x) Enterprise (Core License):

Edition Upgrade FromEdition Upgrade To
SQL Server 2017 (14.x) Enterprise (Server+CAL License)**SQL Server 2017 (14.x) Enterprise (Core License)
SQL Server 2017 (14.x) Enterprise (Core License)SQL Server 2017 (14.x) Enterprise (Server+CAL License)

Sql Server Express Versions List

* Also applies to SQL Server 2017 (14.x) Express with Tools and SQL Server 2017 (14.x) Express with Advanced Services.

** Changing the edition of a SQL Server 2017 (14.x) failover cluster is limited. The following scenarios are not supported for SQL Server 2017 (14.x) failover clusters:

  • SQL Server 2017 (14.x) Enterprise to SQL Server 2017 (14.x) Developer, Standard, or Evaluation.

  • SQL Server 2017 (14.x) Developer to SQL Server 2017 (14.x) Standard or Evaluation.

  • SQL Server 2017 (14.x) Standard to SQL Server 2017 (14.x) Evaluation.

  • SQL Server 2017 (14.x) Evaluation to SQL Server 2017 (14.x) Standard.

Sql Management Studio 2017 Versions

See Also