Microsoft SQL Server English RTM 2017

SQL Server 2017 Release Notes his topic describes limitations and issues with SQL Server 2017. For related information, see:

• Wha t's New in SQL Server 2017
  
• SQL Server on Linux release notes
  

Try SQL Server!

• ][/url] Download SQL Server 2017
  
• [/url] Spin up a Virtual Machine with SQL Server 2017
  

SQL Server 2017 - general availability release (October 2017)
Database Engine

• Issue and customer impact: After upgrade, the existing FILESTREAM network share may be no longer available.
  
  
• Workaround: First, reboot the computer and check if the FILESTREAM network share is available. If the share is still not available, do the following:
  
  
  • In SQL Server Configuration Manager, right click the SQL Server instance, and click Properties.
    
  • In the FILESTREAM tab clear Enable FILESTREAM for file I/O streaming access , then click Apply.
    
  • Check Enable FILESTREAM for file I/O streaming access again with the original share name and click 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 cannot be saved. The object guid is not valid"
  
  
• Workarounds:
  
  
  • Grant permission on the sub nodes in the tree view instead of the root level.
    
  • or
    
  • Run the script described in this MDS team blog error applying permission on entity level
    
  
  
  

Analysis Services

• Issue and customer impact: For tabular models at the 1400 compatibility level, when using Get Data, data connectors for some data sources such as Amazon Redshift, IBM Netezza, and Impala, are not yet available.
  
• 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 re-deploy.
  

Tools

• Issue and customer impact: Running DReplay fails with the following message: "Error DReplay Unexpected error occurred!".
  
• Workaround: None.
  

SQL Server 2017 Release Candidate (RC2 - August 2017)
There are no SQL Server on Windows release notes for this release. See SQL Server on Linux Release notes.



SQL Server 2017 Release Candidate (RC1 - July 2017)
SQL Server Integration Services (SSIS) (RC1 - July 2017)

• Issue and customer impact: The parameter runincluster of the stored procedure [catalog].[create_execution] is renamed to runinscaleout for consistency and readability.
  
• Workaround: If you have existing scripts to run packages in Scale Out, you have to change the parameter name from runincluster to runinscaleout to make the scripts work in RC1.
  
  
• Issue and customer impact: SQL Server Management Studio (SSMS) 17.1 and earlier versions can't trigger package execution in Scale Out in RC1. The error message is: "@runincluster is not a parameter for procedure create_execution." This issue is fixed in the next release of SSMS, version 17.2. Versions 17.2 and later of SSMS support the new parameter name and package execution in Scale Out.
  
  
• Workaround: Until SSMS version 17.2 is available:
  
  
  • Use your existing version of SSMS to generate the package execution script.
    
  • Change the name of the runincluster parameter to runinscaleout in the script.
    
  • Run the script.
    
  
  
  

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 is 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 not 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.
  
  
  • Launch a command prompt in Administrator mode.
    
  • 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
    
    
  • Then go to the next folder, which is either SSRS or PBIRS depending on what is remaining.
    
    
  • Go to the WMI folder.
    
  • Run the following command:
    
    regsvr32 /i ReportingServicesWMIProvider.dll
    
    If you see the following error, ignore 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 computer 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 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:
  
  
  • Go to Add/Remove Programs
    
  • Find Microsoft SQL Server vNext T-SQL Language Service CTP2.1, right-click it, and select Uninstall.
    
  • After the component is removed, repair the application that is broken or reinstall the appropriate version of TSqlLanguageService.MSI.
    
    This workaround removes 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.
    
  
  
  

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 is 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.
  

• User upgrades SQL Server instance hosting secondary replica in accordance with best practices.
  
• After upgrade, a failover occurs and a 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.
  
• 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.
  

.SpoilerTarget">Spoiler: What's new in SQL Server 2017 SQL Server 2017 represents a major step towards making SQL Server a platform that gives you choices of development languages, data types, on-premises or cloud, and operating systems by bringing the power of SQL Server to Linux, Linux-based Docker containers, and Windows. This topic summarizes what is new for specific feature areas and includes links to additional details.

[url=[/url] Try it out: Download SQL Server 2017 Release - October 2017:.

Run SQL Server on Linux! For more information, see SQL Server on Linux Documentation.

SQL Server 2017 Database Engine
SQL Server 2017 includes many new Database Engine features, enhancements, and performance improvements.

Check Sum
67a5ffd3789c3d01821443c994c66d1a *en_sql_server_2017_developer_x64_dvd_11296168.iso
172d85fcaaa121a061b82193cb90e54f *en_sql_server_2017_enterprise_core_x64_dvd_11293037.iso
69f8311173e54b4c899a58e56be21853 *en_sql_server_2017_enterprise_x64_dvd_11293666.iso
e7598a375e7beeefcfaeae6399bdf6d4 *en_sql_server_2017_express_with_advanced_services_x64_11301593.exe
409d2384684cd6a45c64bdd5414fbf24 *en_sql_server_2017_express_x64_11301593.exe
d180ae500607f6eae8942eaa285d8a06 *en_sql_server_2017_localdb_x64_11301593.msi
ed7128b1b88953d1b08a7c1acfa8d928 *en_sql_server_2017_standard_x64_dvd_11294407.iso
38b634c513a713fec93055f68444d105 *en_sql_server_2017_web_x64_dvd_11293612.iso

Keys
[You must be registered and logged in to see this link.]