KB3182545 - SQL Server 2016 Service Pack 1 release information
Release Date: November 16, 2016
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.
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.
Known issues in this service pack
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.
Install the hotfix in KB 3207512 to address these issues.
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'll need to reapply the customization.
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's 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:
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.
- 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.
For more information about the bugs that are fixed in SQL Server 2016 SP1, go to the following Microsoft Knowledge Base articles.
Resolutions to the following issues are also included in SQL Server 2016 SP1.
|NULL values are ignored when altering the data type of a column from text to varchar(max).
|Sqlcmd quits without error if the query text contains both embedded comments and curly braces
|Batch sort and optimized nested loop may cause stability and performance issues.
|Table scans and index scans with push-down predicate tend to overestimate memory grant for the parent operator.
|The Full-Text Search feature doesn't work as expected for Dutch language.
CREATE NONCLUSTERED INDEX statement may fail if the database name begins with a '
|Add informational messages for
tempdb configurations in the SQL Server error log.
MERGE statements that contain both
INSERT statements fail with "Cannot insert duplicate key row" if the destination table contains unique index.
|SQL Server crashes when a Tuple Mover task is terminated unexpectedly.
|Add the table name and Primary Key value information for error 20598 in the
msdistribution_history table (SQL Server Replication).
|When a replication agent fails with query timeout, the query text is logged without verbose logging enabled.
|The Replication Log Reader Agent may fail when destination table is an empty string.
|Update the copyright information to '© 2016 Microsoft' in the SQL Server command prompt installation.
|Unnecessary warning message is returned in the command line output when slipstream installs SQL Server with command line option.
|After you removed one or more updates for SQL Server, when you repair SQL Server, the repair operation fails with errors.
|Install SQL Server on a computer that has a non-English domain name will fail with error 'Illegal characters in path'.
|The string 'Setup Discovery Report' in the 'Installed SQL Server features discovery report' isn't localized.
|SQL Server 2016 installation wizard incorrectly mentioned SQL Server 2008 SP3 while SQL 2008 R2 SP3 is required.
|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.
|The setup of SQL Server 2016 may fail if ODBC Driver 11 for SQL Server is installed during the setup.
|A slipstream installation may fail with the 'Strong name validation failed' error.
UpdateEnabled is set to
False in a slipstream installation, the setup summary log doesn't contain the information of the updates installed during the installation.
|BCP fails with error when parsing date format
YYYY/MM/DD into a
|Standard edition of SQL Server 2016 Analysis Services (Tabular mode) ignores the 16 GB memory limit.
|Queries that contain Row-Level Security (RLS) may fail even if the DataView is set to Sample.
|Affinity mask doesn't work correctly for NUMA nodes in SQL Server 2016 Analysis Services.
|Improve SSAS Tabular performance scalability by implementing NUMA awareness in SSAS Tabular mode.
|Improve SSAS Tabular performance scalability by using Intel® Threading Building Blocks (Intel® TBB).
|Error "Log provider 'Microsoft.LogProviderEventLog' is not installed" occurs when you open the Configure SSIS Logs: Package dialog in an SSIS package that already has a log.
|This update changes the behavior that when the XML Task can't get encoding from the XML documents, Unicode encoding will be used.
|Adds additional information to indicate whether a report is a Mobile report to the SSRS report server execution logs.
|You may need to retry reauthorization if data reconciliation fails on a Stretch Database enabled table.
|Query execution may fail on a Stretch Database enabled table that has filter predicate specified.
|Creating, altering or dropping indexes on a table with Stretch Database enabled may fail.
For more information about how to upgrade your SQL Server installation to SQL Server 2016 SP1, see Supported version and edition upgrades.
How to get SQL Server 2016 SP1
SQL Server 2016 SP1 is available for download at the SQL Server 2016 SP1 download page.
After you install the service pack, the SQL Server service version should be reflected as 13.0.4422.0.
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 isn't blocked and you'll be able to uninstall SQL Server 2016 SP1 like any other service pack. However, if you're 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's 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 isn't possible to drop memory_optimized_data filegroup. Hence if you have setup
memory_optimized_data filegroup on your database with SP1, you shouldn't uninstall SQL Server 2016 SP1 in that case else the database will get in suspect mode with following error message logged in the error log:
<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.
This product contains software derived from the Xerox Secure Hash Function.
This product includes software from the zlib general purpose compression library.
Parts of this software are based in part on the work of RSA Data Security, Inc. Because Microsoft has included the RSA Data Security, Inc., software in this product, Microsoft is required to include the text below that accompanied such software:
- Copyright 1990, RSA Data Security, Inc. All rights reserved.
- License to copy and use this software is granted provided that it's identified as the "RSA Data Security, Inc., MD5 Message-Digest Algorithm" in all material mentioning or referencing this software or this function. License is also granted to make and use derivative works provided that such works are identified as "derived from the RSA Data Security, Inc., MD5 Message-Digest Algorithm" in all material mentioning or referencing the derived work.
- RSA Data Security, Inc., makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It's provided "as is" without express or implied warranty of any kind.
These notices must be retained in any copies of any part of this documentation or software.
The Reporting Services mapping feature uses data from TIGER/Line Shapefiles that are provided courtesy of the United States Census Bureau. TIGER/Line Shapefiles are an extract of selected geographic and cartographic information from the Census MAF/TIGER database. TIGER/Line Shapefiles are available without charge from the United States Census Bureau. To get more information about the TIGER/Line shapefiles, go to TIGER/Line shapefiles. The boundary information in the TIGER/Line Shapefiles is for statistical data collection and tabulation purposes only; its depiction and designation for statistical purposes doesn't constitute a determination of jurisdictional authority, rights of ownership, or entitlement, and doesn't reflect legal land descriptions. Census TIGER and TIGER/Line are registered trademarks of the United States Census Bureau.
Copyright 2012 Microsoft. All rights reserved.
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:
321185 How to identify your SQL Server version and edition
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.