KB4052908 - SQL Server 2016 Service Pack 2 release information
Release Date: April 24, 2018
This article contains important information to read before you install Microsoft SQL Server 2016 Service Pack 2 (SP2). 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.
List of fixes included in SQL Server 2016 SP2
Microsoft SQL Server 2016 service packs are cumulative updates. SQL Server 2016 SP2 upgrades all editions and service levels of SQL Server 2016 to SQL Server 2016 SP2. In addition to the fixes that are listed in this article, SQL Server 2016 SP2 includes hotfixes that were included in SQL Server 2016 Cumulative Update 1 (CU1) to SQL Server 2016 SP1 CU8.
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 SP2, go to the following Microsoft Knowledge Base articles.
Resolutions to the following issues are also included in SQL Server 2016 SP2.
|Adds durable memory-optimized tables that can have foreign key reference to nondurable memory-optimized tables.
SpLevel and ReleaseProductVersion properties to SQL Server 2016 SP1.
|Setup & Install
|Fixes an issue by installing a SQL Server security update on the passive node in a customized cluster.
|Setup & Install
|Fixes an issue to avoid null reference in
|Adds a DVM
sys.dm_tran_version_store_space_usage that can track the
tempdb version store usage in each database.
|Fixes an issue in which the plan cache memory usage is high when the
MAXDOP is set to
|Adds a new DMV
sys.dm_db_log_stats that returns summary level attributes and information about transaction log files of databases.
|Adds a new DMV
sys.dm_db_log_info that returns the Virtual Log File (VLF) information about the transaction log files.
|Exposes the percentage of differential changes in the databases to help determine whether full database backup or differential backup is useful.
|Adds a new DMV
sys.dm_tran_version_store_space_usage that returns a table to display total space in tempdb used by version store records for each database.
|Fixes an issue in which restoring a compressed backup for a Transparent Data Encryption (TDE) enabled database through the Virtual Device Interface (VDI) interface may fail with the operating system error 38.
|Adds the filegroup support to the
SELECT INTO statement. This allows you to specify the name of the filegroup in which a new table will be created. The filegroup specified should exist on the database else the SQL Server engine throws an error.
WITH VERIFY_CLONE option and the
WITH BACKUP_CLONE option to the
DBCC CLONEDATABASE management command that allows you to verify and back up cloned databases.
|Exposes the processor information such as core count, sockets, and NUMA information in DMV
sys.dm_server_services and the
|Improves the backup performance on computers that have large memory.
|Adds a database name attribute in the process-list and
executionStack in the extended event
xml_deadlock_report to expose the database name.
|Adds a new extended event
marked_transaction_latch_trace that shows the state of the global latches that are used by marked transactions.
|Improves the Distributed Transaction Coordinators (DTC) service support for AlwaysOn availability groups (AG) databases.
|Fixes an issue in which you're unable to run the
ADDNODE step when the Polybase feature is installed in ScaleOut deployment mode.
|Exposes the last-known good
DBCC CHECKDB date and time for a database.
|Fixes an issue by removing a node from a failover cluster that has Polybase installed.
|Fixes an issue in which the DMV
sys.dm_exec_query_profiles shows an incorrect result that's inconsistent with the estimated or actual query plan.
|Fixes the memory grant usage (
UsedMemoryGrant properties) in Showplan XML for parallel queries.
|Fixes an issue in which the
MAX_GRANT_PERCENT query hint isn't always being respected.
|Fixes an issue in which an assertion error might occur when you query the DMV
sys.dm_db_stats_histogram if the
TIMESTAMP column contains values.
For more information about how to upgrade your SQL Server installation to SQL Server 2016 SP2, see Supported version and edition upgrades.
How to get SQL Server 2016 SP2
SQL Server 2016 SP2, Microsoft SQL Server 2016 SP2 Express, and Microsoft SQL Server 2016 SP2 Feature Pack are available for manual download and installation at the following Microsoft Download Center websites.
After you install the service pack, the SQL Server service version should be 13.0.5026.0 Microsoft SQL Server 2016 service packs are cumulative updates. SQL Server 2016 SP2 upgrades all editions and service levels of SQL Server 2016 to SQL Server 2016 SP2.
Uninstalling SQL Server 2016 SP2 (not recommended)
If, for any reason, you choose to uninstall SQL Server 2016 SP2, the uninstallation of SQL Server 2016 SP2 will not be blocked, and you will be able to uninstall SQL Server 2016 SP2 in the same manner as any other service packs. However, if you are running the Standard, Web, or Express edition of SQL Server, and you are using some new features that are unlocked only when you start SQL Server 2016 SP2, you might experience errors or see databases left in a suspect state after the uninstallation of SQL Server 2016 SP2. Even worse, if the system databases are using new features (for example, partitioned tables in master databases), this could prevent SQL Server instances from starting after you uninstall SQL Server 2016 SP2.
We recommend that you verify that all the new features are disabled or dropped before you choose to uninstall SQL Server 2016 SP2 on editions other than the Enterprise edition. You can't drop the memory_optimized_data filegroup. Therefore, if you have set up the
memory_optimized_data filegroup on your database with SP2, you should not uninstall SQL Server 2016 SP2. Otherwise, the database will get into a suspect state, and the following entry will be 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.