Skip to content

Latest commit

 

History

History
91 lines (58 loc) · 4.06 KB

sql-server-2017-release-notes.md

File metadata and controls

91 lines (58 loc) · 4.06 KB
title description author ms.author ms.reviewer ms.date ms.service ms.subservice ms.topic monikerRange
SQL Server 2017 Release Notes
This article describes limitations and issues with SQL Server 2017 and provides links to related information.
MikeRayMSFT
mikeray
randolphwest
03/06/2025
sql
release-landing
release-notes
>=sql-server-2016

SQL Server 2017 release notes

[!INCLUDE SQL Server 2017]

This article describes limitations and issues with SQL Server 2017. For related information, see:

Try SQL Server

:::image type="icon" source="../includes/media/download.svg" border="false"::: Download SQL Server 2017

:::image type="icon" source="../includes/media/azure-vm.svg" border="false"::: Spin up a Virtual Machine with SQL Server 2017

Note

[!INCLUDE sssql22-md] is available. For more information, see What's new in SQL Server 2022.

Azure Connect Pack for SQL Server 2017 (March 2025)

Adds support for the link feature for Azure SQL Managed Instance, which enables database replication from SQL Server to Azure SQL Managed Instance.

For more information, see Azure Connect Pack for SQL Server 2017.

General availability release (October 2017)

Database Engine

  • Issue and customer impact: After upgrade, the existing FILESTREAM network share might be no longer available.

  • Workaround: First, restart the computer and check if the FILESTREAM network share is available. If the share is still not available, complete the following steps:

    1. In SQL Server Configuration Manager, right-click the SQL Server instance, and select Properties.
    2. In the FILESTREAM tab clear Enable FILESTREAM for file I/O streaming access, then select Apply.
    3. Check Enable FILESTREAM for file I/O streaming access again with the original share name and select Apply.

Master Data Services (MDS)

  • Issue and customer impact:

    On the user permissions page, when granting permission to the root level in the entity tree view, you see the following error: "The model permission can't be saved. The object guid isn't valid"

  • Workaround:

    • Grant permission on the sub nodes in the tree view instead of the root level.

Analysis Services

  • Issue and customer impact: Data connectors for the following sources aren't yet available for tabular models at the 1400 compatibility level.

    • Amazon Redshift
    • IBM Netezza
    • Impala
  • Workaround: None.

  • Issue and customer impact: Direct Query models at the 1400 compatibility level with perspectives can fail on querying or discovering metadata.

  • Workaround: Remove perspectives and redeploy.

Tools

  • Issue and customer impact: Running DReplay fails with the following message:

    Error DReplay Unexpected error occurred!
    
  • Workaround: None.

More information

[!INCLUDE get-help-options]