KB4577775 - Cumulative Update 15 for SQL Server 2016 SP2

Work anywhere from any device with Microsoft 365

Upgrade to Microsoft 365 to work anywhere with the latest features and updates.

Upgrade now

Known issue

There is a known issue with the SQL Writer component in SQL Server 2016 SP2 CU15. The SQL Writer service is shared across all instances of SQL Server that run on the same server, regardless of version. If you have installed this cumulative update on a server that also runs older versions of SQL Server, such as SQL Server 2014 or SQL Server 2012, VSS backups will fail against these older instances. If you are running SQL Server 2016 side-by-side with older versions of SQL Server, we recommend that you do not install this Cumulative Update. This issue will be fixed in the next Cumulative Update release.


This article describes Cumulative Update package 15 (CU15) (build number: 13.0.5850.14) for Microsoft SQL Server 2016 Service Pack 2 (SP2). This update contains fixes that were released after the initial release of SQL Server 2016 SP2.

About cumulative updates for SQL Server

Cumulative updates (CU) are now available at the Microsoft Download Center.

Only the most recent CU that was released for SQL Server 2016 SP2 is available at the Download Center. Each new CU contains all the fixes that were included togetrher with the previous CU for the installed version or service pack of SQL Server. For a list of the latest cumulative updates for SQL Server, see the following article:


  • Microsoft recommends ongoing, proactive installation of CUs as they become available:

    • SQL Server CUs are certified to the same levels as Service Packs, and should be installed at the same level of confidence.

    • Historical data shows that a significant number of support cases involve an issue that has already been addressed in a released CU.

    • CUs may contain added value over and above hotfixes. This includes supportability, manageability, and reliability updates.

  • Just as for SQL Server service packs, we recommend that you test CUs before you deploy them to production environments.

  • We recommend that you upgrade your SQL Server installation to the latest SQL Server 2016 service pack.

How to obtain this cumulative update package

The following update is available from the Microsoft Download Center:

Download icon  Download the latest cumulative update package for SQL Server 2016 SP2 now.
If the download page does not appear, contact Microsoft Customer Service and Support to obtain the cumulative update package.

Note After future cumulative updates are released for SQL Server 2016, this CU can be located and downloaded from the Microsoft Windows Update Catalog. However, we recommend that you always install the latest cumulative update that is available.

Additional hotfixes that are included in this cumulative update package

Bug reference

KB article number


Fix area



Intermittent error 6552 occurs when running Spatial query with TOP <param> or OFFSET <param1> ROWS FETCH NEXT <param2> ROWS ONLY clause and parallel plan

SQL Engine



Query Store scalability improvement for adhoc workloads. Query Store now imposes internal limits to the amount of memory, it can use and automatically changes the operation mode to READ-ONLY until enough memory has been returned to the Database Engine, preventing performance issues.

SQL Engine




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

SQL Engine




FIX: Incorrect results occur when you run INSERT INTO SELECT statement on memory-optimized table variables in SQL Server 2016

In-Memory OLTP



Fixes an issue where the session gets killed when you run DBCC CHECKTABLE with PHYSICAL_ONLY due to disk full. The session remains in KILLED\ROLLBACK state and threads are waiting on CHECK_TABLES_THREAD_BARRIER wait type with increasing wait time.

SQL Engine



Unable to connect to primary database replica after failing over the Availability Group in SQL Server 2016

High Availability



When using FileTables in SQL Server, you may notice dumps being generated periodically that contain an assertion in function FFtFileObject::ProcessPostCreate. In some environments, these dumps may trigger a failover.
FFtFileObject::ProcessPostCreate file = FileName line = LineNumber expression = FALSE

SQL Engine




FIX: Incorrect results can occur when you run linked server query with aggregates or joins on table with filtered index on a remote server in SQL Server 2016 and 2017

SQL performance



When you run a RESTORE HEADERONLY of SQL Server 2016 backup, you may notice error 3285 even if the correct blocksize has been specified. If the error persists after applying this fix, you may specify the proper blocksize or contact Microsoft Support for assistance.

SQL Engine



When you try to restore from a compressed or encrypted backup over an existing TDE enabled database, you may notice that the restore operation may take longer time than expected.

SQL Engine




FIX: Managed backup is not backing up the database when SQL Agent system jobs are changed to different name other than 'sa' in SQL Server 2016 and 2017

SQL Engine



CHECKDB reports no errors but users may see errors 602 and 608 due to inconsistent Full Text metadata.

SQL Engine



When you try to backup a READ-ONLY database that contains memory optimized filegroups and files or filestream objects, the backup fails with errors 3013 and 3906.

SQL Engine



When a VSS backup tries to backup SQL Server databases that are hosted on the forwarder replica of a Distributed Availability Group then the backup operation fails.   

This BACKUP or RESTORE command is not supported on a database mirror or secondary replica.
BACKUP DATABASE is terminating abnormally.

In the error log, you may see the following error:                  DateTime Backup      Error: 3041, Severity: 16, State: 1.
DateTime Backup      BACKUP failed to complete the command BACKUP DATABASE DatabaseName. Check the backup application log for detailed messages.

SQL Engine



VERIFY_CLONEDB prints message 'Clone database verification has failed' for the database if the database name starts with a number.

SQL Engine



When a role user with role filter in SQL Server 2016 Analysis services (SSAS 2016) runs Direct Query, you may receive an error.                                                                  An unexpected error occurred (file 'FileName', line LineNumber, function 'FunctionNameQueryFragment_Source::BuildSourceFragment').

Analysis services




FIX: Assertion error occurs when the Availability Group is failed over manually to another replica in SQL Server 2016

SQL Engine



Non-yielding Scheduler error may occur when query store tries to grow its memory structure during heavy workload.

SQL Engine



When you export a report that has a period (.) in the report name, the exported file name will be truncated.

Reporting services



SSAS 2016 tabular process 'calculate' may take 2-4 times longer time after upgrading to the latest Cumulative Update (CU) for SQL Server 2016 SP2. After the upgrade, the increased time was on the attribute hierarchy processing during the process calculate.

Analysis services


Notes for this update

Hybrid environments deployment

When you deploy the hotfixes to a hybrid environment (such as AlwaysOn, replication, cluster, and mirroring), we recommend that you refer to the following articles before you deploy the update:

Language support

  • SQL Server Cumulative Updates are currently multilingual. Therefore, this cumulative update package is not specific to one language. It applies to all supported languages.

Components (features) updated

One Cumulative Update package includes all available updates for ALL SQL Server 2016 components (features). However, the cumulative update package updates only those components that are currently installed on the SQL Server instance you select to be serviced.  If a SQL Server feature (e.g. Analysis Services) is added to the instance after this CU is applied, you must re-apply this CU to update the new feature to this CU.

Support for this update

If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and to issues that do not qualify for this specific cumulative update package. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the Microsoft support website.

How to uninstall this update

  1. In Control Panel, select View installed updates under Programs and Features.

  2. Locate the entry that corresponds to this cumulative update package under Microsoft SQL Server 2016.

  3. Press and hold (or right-click) the entry, and then select Uninstall.

Cumulative update package information

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.