Related topics
Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


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

Download Download the package now.

SQL Server 2016 SP3 Express

Download Download the package now.

Microsoft SQL Server 2016 SP3 Feature Pack

Download Download the package now.

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.


  • 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




High Availability

Improvement: Availability Group listener without the load balancer in SQL Server 2019, 2017, and 2016



High Availability

FIX: Transaction log isn't truncated on a single node Availability Group in SQL Server



High Availability

FIX: Non-yielding Scheduler error may occur with Always On availability group in Microsoft SQL Server



High Availability

FIX: Log line is verbose when Always On Availability Group has many databases in SQL Server 2019 and 2016


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



Setup & Install

FIX: Setup fails when you install SQL Server on FCI with mount points



SQL Connectivity

Improvement: Enable DNN feature in SQL Server 2019 and 2016 FCI


SQL Engine

INSERT EXEC failed because the stored procedure altered the schema of the target table error in SQL Server 2016



SQL Engine

Improvement: Improve CDC supportability and usability with In-Memory Databases



SQL Engine

Improvement: Size and retention policy are increased in default XEvent trace system_health in SQL Server 2019, 2017, and 2016



SQL Engine

Improvement: New XEvents temp_table_cache_trace and temp_table_destroy_list_trace are created in SQL Server 2019 and 2016



SQL Engine

FIX: Assertion occurs when you access memory-optimized table through MARS in SQL Server 2017 or 2016



SQL Engine

FIX: Error occurs when sp_addarticle is used to add article for transactional replication to memory-optimized table on subscriber in SQL Server 2017 and 2016



SQL Engine

FIX: Geocentric Datum of Australia 2020 is added to SQL Server 2017, 2016, and 2014



SQL Engine

FIX: SQL update package does not update Local DB files correctly when installed using SqlLocalDb.msi



SQL Engine

FIX: Assertion occurs when sys.sp_cdc_enable_table is used to enable CDC on column set table in SQL Server 2017 and 2016



SQL Engine

FIX: Fix incorrect memory page accounting that causes out-of-memory errors in SQL Server



SQL Engine

FIX: Access violation exception occurs when promoting latches of frequently used database pages in SQL Server 2017 and 2016



SQL Engine

FIX: Managed backup fails to take full backup when backup preference is set to secondary on Read-Only secondary in SQL Server 2016



SQL Engine

FIX: Update SQL Server 2017 and 2016 CEIP service to send usage and diagnostic data to a new endpoint



SQL Engine

FIX: SQLLocalDB.exe info doesn't display information about the specified LocalDB instance if SQL LocalDB 2016 SP2 is installed



SQL Engine

FIX: "SQLLocalDB.exe versions" stops listing the versions of LocalDB installed on the computer if SQL LocalDB 2016 SP1/SP2 is installed


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
Operations that scan SQL Server buffer pool are slow on large memory machines | Microsoft Learn


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 =
FilePath\FileName line = LineNumber expression = m_state == XDES_COMMITTED


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



SQL Performance

Improvement: Enhancement adds sql_statement_post_compile XEvent in SQL Server 2017 and 2016




SQL Performance

Improvement: Corrupt statistics can be detected by using extended_logical_checks in SQL Server 2019 and 2016


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



SQL Security

FIX: SQL Server fails to start with error messages when an incorrect certificate is provisioned for SSL

File name

SHA256 hash





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


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.

Was this information helpful?

What affected your experience?

Thank you for your feedback!