This article contains important information to read before you install Microsoft SQL Server 2016 Service Pack 1(SP1). It describes how to get the service pack, the list of fixes that are included in the service pack, known issues, and a list of copyright attributions for the product.
Note This article serves as a single source of information to locate all documentation that's related to this service pack. It includes all the information that you previously found in the release notes and Readme.txt files.
Note This article serves as a single source of information to locate all documentation that's related to this service pack. It includes all the information that you previously found in the release notes and Readme.txt files.
More Information
How to get SQL Server 2016 SP1
SQL Server 2016 SP1 is available for download at the SQL Server 2016 SP1 download page. You can download SQL Server 2016 SP1 Feature Pack here.Note After you install the service pack, the SQL Server service version should be reflected as 13.0.4422.0.
List of fixes included in SQL Server 2016 SP1
Microsoft SQL Server 2016 service packs are cumulative updates. SQL Server 2016 SP1 upgrades all editions and service levels of SQL Server 2016 to SQL Server 2016 SP1. In addition to the fixes that are listed in this article, SQL Server 2016 SP1 includes hotfixes that were included in SQL Server 2016 Cumulative Update 1 (CU1) to SQL Server 2016 CU3.For more information about the cumulative updates that are available in SQL Server 2016, see SQL Server 2016 build versions .
Notes
- Additional fixes that aren't documented here may also be included in the service pack.
- This list will be updated when more articles are released.
Additional resolutions
Resolutions to the following issues are also included in SQL Server 2016 SP1.| VSTS bug number | Description | Area |
|---|---|---|
| 4300066 | Update the copyright information to '© 2016 Microsoft' in the SQL Server command prompt installation. | Setup |
| 5128484 | Standard edition of SQL Server 2016 Analysis Services (Tabular mode) ignores the 16 GB memory limit | SSAS |
| 5610151 | Unnecessary warning message is returned in the command line output when slipstream install SQL Server with command line option. | Setup |
| 6867499 | NULL values are ignored when altering the data type of a column from text to varchar(max). | Engine |
| 7270486 | After you removed one or more updates for SQL Server, when you repair SQL Server, the repair operation fails with errors. | Setup |
| 7330691 | Adds additional information to indicate whether a report is a Mobile report to the SSRS report server execution logs. | SSRS |
| 7350315 | Install SQL Server on a computer that has a non-English domain name will fail with error 'Illegal characters in path'. | Setup |
| 7439317 | The string 'Setup Discovery Report' in the 'Installed SQL Server features discovery report' is not localized. | Setup |
| 7439502 | SQL Server 2016 installation wizard incorrectly mentioned SQL Server 2008 SP3 while SQL 2008 R2 SP3 is required. | Setup |
| 7487320 | Queries contain Row-Level Security (RLS) may fail even the DataView is set to Sample. | SSAS |
| 7807395 | You may need to retry reauthorization if data reconciliation fails on a Stretch Database enabled table. | Stretch DB |
| 8024962 | Sqlcmd quits without error if the query text contains both embedded comments and curly braces ("{" or "}"). | Engine |
| 8024968 | Batch sort and optimized nested loop may cause stability and performance issues. | Engine |
| 8024972 | BCP fails with error when parse date format YYYY/MM/DD into a DATE column. | |
| 8024974 | NULL values are ignored when altering the data type of a column from text to varchar(max). | Engine |
| 8024987 | Table scans and index scans with push down predicate tend to overestimate memory grant for the parent operator. | Engine |
| 8024994 | On the Complete tab, the link to the 'Surface Area Configuration' MSDN documentation is missing from the Document and Links section in a slipstream installation. | Setup |
| 8024997 | The Full-Text Search feature does not work as expected for Dutch language. | Engine |
| 8024998 | Error "Log provider 'Microsoft.LogProviderEventLog' is not installed" occurs when you open the Configure SSIS Logs: Package dialog in a SSIS package that already has a log. | SSIS |
| 8025032 | This update change the behavior that when the XML Task cannot get encoding from the XML documents, Unicode encoding will be used. | SSIS |
| 8025058 | Add the table name and Primary Key value information for error 20598 in the msdistribution_history table (SQL Server Replication) | Improvement |
| 8025059 | When a replication agent fails with query timeout, the query text is logged without enable verbose logging. | Replication |
| 8025069 | The CREATE NONCLUSTERED INDEX statement may fail if the database name begins with a '#' character. | Engine |
| 8025081 | The Replication Log Reader Agent may fail when destination table is an empty string. | Replication |
| 8025097 | Add informational messages for tempdb configurations in SQL Server error log. | Engine |
| 8051010 | The setup of SQL Server 2016 may fail if ODBC Driver 11 for SQL Server is installed during the setup. | Setup |
| 8196154 | Query execution may fail on a Stretch Database enabled table that has filter predicate specified. | Stretch DB |
| 8210484 | Affinity mask does not work correctly for NUMA nodes in SQL Server 2016 Analysis Services. | SSAS |
| 8267453 | MERGE statements that contain both UPDATE and INSERT statements fail with "Cannot insert duplicate key row" if the destination table contains unique index. | Engine |
| 8279683 | SQL Server crashes when a Tuple Mover task is terminated unexpectedly. | Engine |
| 8281121 | Improve SSAS Tabular performance scalability by implement NUMA awareness in SSAS Tabular mode. | SSAS |
| 8292093 | Create, alter or drop indexes on a table with Stretch Database enabled may fail. | Stretch DB |
| 8343905 | A slipstream installation may fail with the 'Strong name validation failed' error. | Setup |
| 8348718 | If updateenabled is set to false in a slipstream installation, the setup summary log does not contain the information of the updates installed during the installation. | Setup |
| 8430619 | Improve SSAS Tabular performance scalability by using Intel® Threading Building Blocks (Intel® TBB). | SSAS |
For more information about how to upgrade your SQL Server installation to SQL Server 2016 SP1, see Supported Version and Edition Upgrades.
Known issues
SQL Server Reporting Services
After you install SQL Server 2016 SP1, you may encounter the following issues when you use SQL Server Reporting Services:- If Reporting Services is set to use a secure (https/SSL) connection, a warning about security content may be displayed.
- In certain scenarios, the Print button stops working.
SQL Server Integration Services (SSIS)
After you install SQL Server 2016 SP1, the DCOM permissions for launching and accessing Integration Services service are reset to default permissions. If you have customized DCOM permissions, you will need to reapply the customization. The issue is under investigation and fix for the issue is not available but users can use the workaround described in KB 2000474.ODBC Driver 13.1
With the default installation of SQL Server 2016, ODBC Driver 13.0 is installed on the server which is used by SQL Agent and SSMS (installed on server) to connect to the SQL Server instance. If you have installed ODBC Driver 13.1 on your server for any reason, SQL Server 2016 SP1 installation overrides the ODBC Driver 13.1 installation and the fixes introduced in 13.1 like KB 3185365 may be lost. In this case post installation of SQL Server 2016 SP1, it is recommended to uninstall the ODBC Driver installed by SQL Server 2016 SP1 and install ODBC Driver 13.1.To check for ODBC Driver installed on the server, you can go to Control Panel of the server –> Programs and Features –> Search for ODBC. The version number of ODBC Driver 13.1 is 13.1.811.168 as shown below:
Uninstalling SQL Server 2016 SP1 (Not recommended)
If for any reason you choose to uninstall SQL Server 2016 SP1, the uninstallation of SQL Server 2016 SP1 is not blocked and you will be able to uninstall SQL Server 2016 SP1 like any other service pack. However, if you are running Standard, Web, Express edition of SQL Server and leveraging some of the new features which are unlocked only starting SQL Server 2016 SP1, you might see some unforeseen errors or databases might even be left in suspect state after uninstallation of SQL Server 2016 SP1. Even worse would be if the system databases are using new features for example, partitioned table in master database, it can lead to SQL Server instance unable to start after uninstalling SQL Server 2016 SP1. Hence it is recommended to validate all the new features are disabled or dropped before you choose to uninstall SQL Server 2016 SP1 on editions other than Enterprise Edition. It is not possible to drop memory_optimized_datafilegroup. Hence if you have setup memory_optimized_data filegroup on your database with SP1, you should not uninstall SQL Server 2016 SP1 in that case else the database will get in suspect mode with following error message logged in Errorlog:<DateTime> spid15s Error: 41381, Severity: 21, State: 1.
<DateTime> spid15s The database cannot be started in this edition of SQL Server because it contains a MEMORY_OPTIMIZED_DATA filegroup. See Books Online for more details on feature support in different SQL Server editions.
<DateTime> spid15s The database cannot be started in this edition of SQL Server because it contains a MEMORY_OPTIMIZED_DATA filegroup. See Books Online for more details on feature support in different SQL Server editions.
References
For more information about how to determine the current SQL Server version and edition, select the following article number to go to the article in the Microsoft Knowledge Base:
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.