KB3182545 - SQL Server 2016 Service Pack 1 release information

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.

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.

For more information about the bugs that are fixed in SQL Server 2016 SP1, go to the following Microsoft Knowledge Base articles.

VSTS bug number

KB Article

Description

8025045

2925865

Error when you execute SSIS package on FIPS-enabled Windows

8025041

3065060

FIX: "Unable to create restore plan due to break in the LSN chain" error when you restore differential backup in SSMS

8024976

3100256

"Log provider "Microsoft.LogProviderSQLServer" is not installed correctly" error when you open the Configure SSIS Logs window

8025018

3107397

Improved diagnostics for query execution plans that involve residual predicate pushdown in SQL Server

8024991

3112704

FIX: Missing columns aren't specified in the error message when you import data by using the Import and Export Wizard

8529432

3168708

FIX: SQL Server Managed Backup to Windows Azure tries to back up database snapshots in SQL Server

8025131

3170015

DMV sys.dm_os_memory_nodes returns a non-zero value for the pages_kb value for the DAC node in SQL Server 2014

8024984

3170112

Update to expose maximum memory enabled for a single query in Showplan XML in SQL Server 2014 or 2016

8024978

3170114

Update to add DMF sys.dm_db_incremental_stats_properties in SQL Server 2014 or 2016

8024985

3170115

Information about enabled trace flags is added to the showplan XML in SQL Server 2014 SP2 or 2016

8025056

3170116

FIX: Memory grant that's required to run optimized nested loop join isn't reflected in Showplan XML in SQL Server 2014 or 2016

7994008

3170123

Supports DROP TABLE DDL for articles that are included in transactional replication in SQL Server 2014 or in SQL Server 2016 SP1

8024963

3172997

Update to add a memory grant warning to the Showplan XML in SQL Server 2014 or 2016

8024967

3172998

FIX: A severe error when you use the sys.dm_db_uncontained_entities DMV in SQL Server 2014 or 2016

8025088

3173156

Update adds AlwaysOn extended events and performance counters in SQL Server 2014 or 2016

8025128

3173157

Adds a stored procedure for the manual cleanup of the change tracking side table in SQL Server 2014 SP2 or 2016 SP1

8025149

3173766

FIX: DBCC CHECKDB or CHECKTABLE returns false positives for data corruption and assertion failures in SQL Server 2014 or 2016

8343868

3180060

FIX: Queries that use CHANGETABLE use much more CPU in SQL Server 2014 SP1 or in SQL Server 2016

8025125

3189663

FIX: SQL Server error log incorrectly mentions logical processors when soft-NUMA is enabled

7062744

3189687

FIX: "'Salt' attribute for Password is missing in the project manifest" error when you close and reopen a SSIS BI project in SQL Server 2016

8265472

3189709

FIX: Installation of Cumulative Update 1 for SQL Server 2016 fails on a named instance

8103248

3189813

An update is available that introduces a new query hint USE HINT in SQL Server 2016

8103261

3190548

An update to introduce a new Transact-SQL statement CREATE OR ALTER in SQL Server 2016

8103265

3190761

Update to improve diagnostics by expose data type of the parameters for parameterized queries in showplan XML output in SQL Server 2016

8149617

3190762

Update to improve diagnostics for query execution plans that involve residual predicate pushdown in SQL Server 2016

8155425

3190871

A new DynamicManagement Function "sys.dm_exec_query_statistics_xml" is available in SQL Server 2016 Service Pack 1

8338496

3191062

FIX: FileTable directory stops responding when you create multiple files concurrently in SQL Server 2014 or 2016

8110745

3191273

An update is available that adds support for self-referential constraints in the new Referential Integrity Operator in SQL Server 2016

7778636

3191296

An update is available that extends the Trace extended event with security protocol handshake information in SQL Server 2016

8273495

3195825

FIX: Deadlock when you execute a query plan with a nested loop join in batch mode in SQL Server 2014 or 2016

8528563

3197605

FIX: SQL Server 2016 stops responding when you restore databases that contain memory-optimized tables

8349500

3201552

An update is available that adds overall query execution statistics information to the STATISTICS XML output in SQL Server 2016

8274352

3201554

FIX: Long compilation time for a query that contains many distinct operators in SQL Server 2016

7898693

3177838

How to use DBCC CLONEDATABASE to generate a schema and statistics only copy of a user database in SQL Server 2014 SP2 and SQL Server 2016 SP1

N/A

3180087

Poor performance when you run INSERT.. SELECT operations in SQL Server 2016

N/A

3203693

“A digitally signed driver is required” warning when you install SQL Server packages in Windows Server 2016 and Windows 10

N/A

NA

New performance feature that enables accelerate transaction commit times (latency) by up to 2-4X, when employing Storage Class Memory (NVDIMM-N nonvolatile storage)

8451202

4019715

FIX: SQL Server 2016 does not log error messages that have a severity level of 21 for checksum mismatches found in In-Memory OLTP checkpoint files


 

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.

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 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:
  ODBC driver

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.

  • 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 is 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 is 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(http://www.census.gov/). 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 http://www.census.gov/geo/www/tiger. The boundary information in the TIGER/Line Shapefiles is for statistical data collection and tabulation purposes only; its depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority, rights of ownership, or entitlement, and does not reflect legal land descriptions. Census TIGER and TIGER/Line are registered trademarks of the United States Census Bureau.

Copyright 2012 Microsoft. All rights reserved.

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:

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.

Potrebna vam je dodatna pomoć?

Proširite svoje vještine
Istražite osposobljavanje
Prvi koristite nove značajke
Pridružite se Microsoft Insidere

Jesu li ove informacije bile korisne?

Hvala vam na povratnim informacijama!

Hvala vam na povratnim informacijama! Čini se da bi vam pomoglo kad bismo vas povezali s nekim od naših agenata podrške za Office.

×