SQL Server vNext Release Notes

This topic describes limitations and issues with SQL Server 2017. For related informaiton, see the following:

SQL Server vNext CTP 2.0 (April 2017)

Documentation (CTP 2.0)

  • Issue and customer impact: Documentation for SQL Server 2017 is limited and content is included with the SQL Server 2016 documentation set. Content in articles that is specific to SQL Server 2017 will be noted with Applies To.
  • Issue and customer impact: No offline content is available for SQL Server 2017.

Always On availability groups

  • Issue and customer impact: A SQL Server instance hosting an availability group secondary replica crashes if the SQL Server major version is lower than the instance that hosts the primary replica. Affects upgrades from all supported versions of SQL Server that host availability groups to SQL Server SQL Server 2017 CTP 2.0. This happens under the following steps.
  1. User upgrades SQL Server instance hosting secondary replica in accordance with best practices.
  2. After upgrade, a failover occurs and newly upgraded secondary becomes primary before completing upgrade for all secondary replicas in the availability group. The old primary is now a secondary which is lower version than primary.
  3. The availability group is in an unsupported configuration and any remaining secondary replicas might be vulnerable to crash.
  • Workaround Connect to the SQL Server instance hosting the new primary replica and remove the faulty secondary replica from the configuration.

    ALTER AVAILABILITY GROUP agName REMOVE REPLICA ON NODE instanceName

    The instance of SQL Server that hosted the secondary replica recovers.

horizontal_bar

SQL Server vNext CTP 1.4 (March 2017)

Documentation (CTP 1.4)

  • Issue and customer impact: Documentation for SQL Server 2017 is limited and content is included with the SQL Server 2016 documentation set. Content in articles that is specific to SQL Server 2017 will be noted with Applies To.
  • Issue and customer impact: No offline content is available for SQL Server 2017.

horizontal_bar

SQL Server vNext CTP 1.3 (February 2017)

Supported installation scenarios (CTP 1.3)

SQL Server 2017 is intended as a test version only. Production deployments are not supported. It is recommneded you install and test SQL Server 2017 on a virtual machine.

Documentation (CTP 1.3)

  • Issue and customer impact: Documentation for SQL Server 2017 is limited and content is included with the SQL Server 2016 documentation set. Content in articles that is specific to SQL Server 2017 will be noted with Applies To.
  • Issue and customer impact: No offline content is available for SQL Server 2017.

SQL Server Integration Services (SSIS) (CTP 1.3)

CDC components not supported in this CTP release

  • Issue and customer impact: The CDC Control Task, CDC Source, and CDC Splitter in are not supported in this CTP release.
  • Workaround: There is no workaround.

horizontal_bar

SQL Server vNext CTP 1.2 (January 2017)

Supported installation scenarios (CTP 1.2)

SQL Server 2017 is intended as a test version only. Production deployments are not supported. It is recommneded you install and test SQL Server 2017 on a virtual machine.

SQL Server Database Engine (CTP 1.2)

  • Issue and customer impact: In some cases, the MSSQLSERVER service will get stuck in the "Starting" state.
  • Workaround: To work around this issue:
    • Create a dependency between the mssqlserver service and the keyiso service. One way to do this is to run the following from an elevated Command Prompt: sc config mssqlserver depend= keyiso
    • Reboot the computer.

Documentation (CTP 1.2)

  • Issue and customer impact: Documentaion for SQL Server 2017 is limited and content is inlcuded with the SQL Server 2016 documentation set. Content in articles that is specific to SQL Server 2017 will be noted with Applies To:.
  • Issue and customer impact: No offline content is available for SQL Server 2017.

SQL Server Integration Services (SSIS) (CTP 1.2)

Deleting the SSIS Catalog may fail when SSIS Scale Out is installed

Issue and customer impact: When the SSIS Scale Out feature is installed on a computer, deleting the SSISDB catalog database may fail with following error: “Could not drop login 'login' as the user is currently logged in”.

Workaround:

  • On a Scale Out Master computer, run the command “services.msc” to open the Services window. Stop the SQL Server Integration Services Cluster Master service.
  • On Scale Out Worker computers that connect to the master, run the command "services.msc" to open the Services window. Stop the SQL Server Integration Services Cluster Worker service.

You can now delete the SSISDB catalog database.

SQL Server Master Data Services (CTP 1.2)

Transaction may not work when the entity transaction log type is set to attribute

Issue and customer impact: When the entity transaction log type is set to Attribute in Master Data Services (default value is Member), the following scenarios fail:

  • Transactions for entity changes are not shown in the website.
  • Unable to open the Transactions page on the website and reverse a transaction.
  • Unable to update an entity with a transaction annotation, in the website.

Workaround: There is no workaround.

Copy version may not work when Copy only committed version is set to false

  • Issue and customer impact: When the Copy only committed version setting is set to No (default value is Yes), the copy version operation may fail. There is no error message.
  • Workaround: There is no workaround.

horizontal_bar

SQL Server vNext CTP 1.1 (December 2016)

Supported installation scenarios (CTP 1.1)

SQL Server 2017 is intended as a test version only. Production deployments are not supported. It is recommneded you install and test SQL Server 2017 on a virtual machine.

Specifically, while the following scenarios may work for you, they have not been thoroughly tested and are not supported in SQL Server 2017:

  • Uninstall of CTP 1.1.
  • Side by side installation with any other versions of SQL Server.
  • Upgrade from any previous versions of SQL Server.
  • No SQL Server feature pack components are available as part of the SQL Server 2017 installation.

Documentation (CTP 1.1)

  • Issue and customer impact: Documentation for SQL Server 2017 is limited and content is included with the SQL Server 2016 documentation set. Content in articles that is specific to SQL Server 2017 will be noted with Applies To:.
  • Issue and customer impact: No offline content is available for SQL Server 2017.

SQL Server Master Data Services (CTP 1.1)

Transaction may not work when the entity transaction log type is set to attribute

Issue and customer impact: When the entity transaction log type is set to Attribute in Master Data Services (default value is Member), the following scenarios fail:

  • Transactions for entity changes are not shown in the website.
  • Unable to open the Transactions page on the website and reverse a transaction.
  • Unable to update an entity with a transaction annotation, in the website.

Workaround: There is no workaround.

Copy version may not work when Copy only committed version is set to false

  • Issue and customer impact: When the Copy only committed version setting is set to No (default value is Yes), the copy version operation may fail. There is no error message.
  • Workaround: There is no workaround.

SQL Server Integration Services (SSIS) (CTP 1.1)

Deleting the SSIS Catalog may fail when SSIS Scale Out is installed

Issue and customer impact: When the SSIS Scale Out feature is installed on a computer, deleting the SSISDB catalog database may fail with following error: “Could not drop login 'login' as the user is currently logged in”.

Workaround:

  • On a Scale Out Master computer, run the command “services.msc” to open the Services window. Stop the SQL Server Integration Services Cluster Master service.
  • On Scale Out Worker computers that connect to the master, run the command "services.msc" to open the Services window. Stop the SQL Server Integration Services Cluster Worker service.

You can now delete the SSISDB catalog database.

ODBC components are not supported in this CTP release

Issue and customer impact: The ODBC Connection Manager, Source, and Destination are not supported in this CTP release.

Workaround: There is no workaround.

horizontal_bar

info_tip Engage with the SQL Server engineering team

MS_Logo_X-Small