SQL Server 2017 Release Notes

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

SQL Server 2017 CTP 2.1 (May 2017)

Documentation (CTP 2.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 Reporting Services (CTP 2.1)

  • Issue and customer impact: If you have both SQL Server Reporting Services and Power BI Report Server on the same machine and uninstall one of them, you will no longer be able to connect to the remaining report server with Report Server Configuration Manager.
  • Workaround To work around this issue, you must perform the following operations after uninstalling one of the servers.

    1. Launch a command prompt in Administrator mode.
    2. Go to the directory where the remaining report server is installed.

      Default location for Power BI Report Server: C:\Program Files\Microsoft Power BI Report Server

      Default location for SQL Server Reporting Services: C:\Program Files\Microsoft SQL Server Reporting Services

    3. Then go to the next folder. This will either be SSRS or PBIRS depending on what is remaining.

    4. Go to the WMI folder.
    5. Run the following command:

      regsvr32 /i ReportingServicesWMIProvider.dll
      

      You can ignore the following error, if you see it.

      The module "ReportingServicesWMIProvider.dll" was loaded but the entry-point DLLInstall was not found. Make sure that "ReportingServicesWMIProvider.dll" is a valid DLL or OCX file and then try again.
      

TSqlLanguageService.msi (CTP 2.1)

  • Issue and customer impact: After installing on a machine that has a 2016 version of TSqlLanguageService.msi installed (either through SQL Setup or as a standalone redistributable) the v13.* (SQL 2016) versions of Microsoft.SqlServer.Management.SqlParser.dll and Microsoft.SqlServer.Management.SystemMetadataProvider.dll are removed. Any applications that have a dependency on the 2016 versions of those assemblies will then cease to function, giving an error similar to: error : Could not load file or assembly 'Microsoft.SqlServer.Management.SqlParser, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.

    In addition, attempts to reinstall a 2016 version of TSqlLanguageService.msi will fail with the message: Installation of Microsoft SQL Server 2016 T-SQL Language Service failed because a higher version already exists on the machine.

  • Workaround To work around this issue and fix an application that depends on the v13 version of the assemblies follow these steps:

    1. Go to Add/Remove Programs
    2. Find Microsoft SQL Server vNext T-SQL Language Service CTP2.1, right-click it, and select Uninstall.
    3. After the component is removed, repair the application that is broken (or reinstall the appropriate version of TSqlLanguageService.MSI)

      This workaround will remove the v14 version of those assemblies, so any applications that depend on the v14 versions will no longer function. If those assemblies are needed, then a separate installation without any side-by-side 2016 installs is required.

horizontal_bar

SQL Server 2017 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 2017 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 2017 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 2017 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.

info_tip Engage with the SQL Server engineering team

MS_Logo_X-Small