KB5003279 - SQL Server 2016 Service Pack 3 release information
Summary
This article contains important information to read before you install Microsoft SQL Server 2016 Service Pack 3 (SP3). 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.
Known issues with this update
If you use the Change Tracking feature, you might encounter errors. For more information, see KB 5007039 before you apply this update package.
How to get SQL Server 2016 SP3
SQL Server 2016 SP3, Microsoft SQL Server 2016 SP3 Express, and Microsoft SQL Server 2016 SP3 Feature Pack are available for manual download and installation at the following Microsoft Download Center websites.
|
SQL Server 2016 SP3 |
|
|
SQL Server 2016 SP3 Express |
|
|
Microsoft SQL Server 2016 SP3 Feature Pack |
Note After you install this service pack, the SQL Server service version should be 13.0.6300.2. Microsoft SQL Server 2016 service packs are cumulative updates. SQL Server 2016 SP3 upgrades all editions and service levels of SQL Server 2016 to SQL Server 2016 SP3.
List of fixes included in SQL Server 2016 SP3
Microsoft SQL Server 2016 service packs are cumulative updates. SQL Server 2016 SP3 upgrades all editions and service levels of SQL Server 2016 to SQL Server 2016 SP3. In addition to the fixes that are listed in this article, SQL Server 2016 SP3 includes hotfixes that were included in SQL Server 2016 Cumulative Update 1 (CU1) to SQL Server 2016 SP2 CU17.
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 SP3, go to the following Microsoft Knowledge Base articles.
|
VSTS bug number |
KB article number |
Area Path |
Description |
|---|---|---|---|
|
4578579 |
High Availability |
||
|
4515772 |
High Availability |
FIX: Transaction log isn't truncated on a single node Availability Group in SQL Server |
|
|
4541303 |
High Availability |
||
|
5003596 |
High Availability |
||
|
High Availability |
Fixes an access violation exception that may occur when sp_server_diagnostics is executed |
||
|
High Availability |
Fixes an issue that causes the database log_reuse_wait_desc to change to AVAILABILITY_REPLICA when a database is removed from Availability Group |
||
|
Integration Services |
Fixes security vulnerabilities CVE-2015-6420 and CVE-2017-15708 |
||
|
5005686 |
Setup & Install |
FIX: Setup fails when you install SQL Server on FCI with mount points |
|
|
4537868 |
SQL Connectivity |
Improvement: Enable DNN feature in SQL Server 2019 and 2016 FCI |
|
|
SQL Engine |
|||
|
4500511 |
SQL Engine |
Improvement: Improve CDC supportability and usability with In-Memory Databases |
|
|
4541132 |
SQL Engine |
||
|
5003937 |
SQL Engine |
||
|
4046056 |
SQL Engine |
FIX: Assertion occurs when you access memory-optimized table through MARS in SQL Server 2017 or 2016 |
|
|
4493329 |
SQL Engine |
||
|
4506023 |
SQL Engine |
FIX: Geocentric Datum of Australia 2020 is added to SQL Server 2017, 2016, and 2014 |
|
|
4526524 |
SQL Engine |
FIX: SQL update package does not update Local DB files correctly when installed using SqlLocalDb.msi |
|
|
4531386 |
SQL Engine |
||
|
4536005 |
SQL Engine |
FIX: Fix incorrect memory page accounting that causes out-of-memory errors in SQL Server |
|
|
4551720 |
SQL Engine |
||
|
5004059 |
SQL Engine |
||
|
5004466 |
SQL Engine |
||
|
5005453 |
SQL Engine |
||
|
5005687 |
SQL Engine |
||
|
SQL Engine |
Fixes EXCEPTION_INVALID_CRT_PARAMETER exception when you perform INSERT\UPDATE of wide replicated table |
||
|
SQL Engine |
Fixes a memory leak when you use STDistance spatial method with a spatial index |
||
|
SQL Engine |
Fixes the sp_hadr_verify_replication_publisher displaying wrong distribution database name in error message |
||
|
SQL Engine |
Introduces new logging and XEvents to help troubleshoot long-running Buffer Pool scans. For more information, see |
||
|
SQL Engine |
Fixes an issue in which some of the temporary working folders are not cleared when many R queries are run in parallel |
||
|
SQL Engine |
Fixes the following assertion that may cause SQL Server to generate a dump:
RecXdes::AnalyzeLogRecord file = |
||
|
SQL Engine |
Fixes an issue where you are unable to set up Managed Backup on SQL Server 2016 by using Azure SAS credential with a long secret due to SAS expiration |
||
|
SQL Engine |
Enables new logging format for SQL Writer that provides additional troubleshooting data in an easy to read/parse format, along with enhanced control of log verbosity and enabling/disabling. For more information, see SQL Server VSS Writer logging - SQL Server | Microsoft Learn |
||
|
SQL Engine |
Fixes Snapshot Agent performance issue observed on SQL 2016 SP2 CU13 and later |
||
|
SQL Engine |
Fixes a missing data problem in Change Data Capture (CDC) side table and adds more error handling to prevent data loss |
||
|
SQL Engine |
Fixes an issue where you cannot run Machine Learning Services (R scripts) when you slipstream an installation of Microsoft SQL Server 2016 without vc_redist 2015 (msvcp140.dll) |
||
|
SQL Engine |
Fixes an issue where an access violation (AV) occurs and you see keywords EXCEPTION_ACCESS_VIOLATION and FFtFileObject::ProcessSetInfo in the SQL Server error log when you use FileTable feature in SQL Server on the machine that uses Windows Defender Antivirus. Note This issue can occur after Windows Defender updates on Windows 10, version 1607 or a later version, Windows Server 2016, and Windows Server 2019 |
||
|
4480630 |
SQL Performance |
Improvement: Enhancement adds sql_statement_post_compile XEvent in SQL Server 2017 and 2016 |
|
|
4530907 |
SQL Performance |
||
|
SQL Performance |
Makes CPU time and duration reported by xevent query_plan_profile more accurate. For more information, see Query Profiling Infrastructure | Microsoft Learn |
||
|
SQL Performance |
Fixes the Access Violation error that occurs when ALTER INDEX is forced to execute using Query Store |
||
|
SQL Performance |
Fixes a stack overflow issue when yourun a query that has a very large number of UNION clauses |
||
|
SQL Performance |
Fixes an assertion in CQPOnDemandTask::ExecuteQPJob if auto async update statistics is enabled |
||
|
5005689 |
SQL Security |
|
File name |
SHA256 hash |
|---|---|
|
SQLServer2016SP3-KB5003279-x64-ENU.exe |
CAE75F65C7C3C263A7BDBAEF0F4AFD0AE49BAF57C08AB27141A7B26008658A91 |
|
SQLServer2016-SSEI-Expr.exe |
25692917049A856B9CCEA2C1242F42A1A585D3AD94F1F449E93BE183F17C397A |
For more information about how to upgrade your SQL Server installation to SQL Server 2016 SP3, see Supported Version and Edition Upgrades.
If, for any reason, you choose to uninstall SQL Server 2016 SP3, the uninstallation of SQL Server 2016 SP3 will not be blocked, and you will be able to uninstall SQL Server 2016 SP3 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 SP3, you might experience errors or see databases left in a suspect state after the uninstallation of SQL Server 2016 SP3. 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 SP3.
We recommend that you verify that all the new features are disabled or dropped before you choose to uninstall SQL Server 2016 SP3 on editions other than the Enterprise edition. You cannot drop the memory_optimized_data filegroup. Therefore, if you have set up the memory_optimized_data filegroup on your database with SP3, you should not uninstall SQL Server 2016 SP3. 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.
To learn how to install SQL Server 2016 R Services on Windows, see Install SQL Server 2016 R Services
-
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. 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 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.
Need more help?
Want more options?
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.
