Cumulative Update 4 for SQL Server 2014 SP2

Applies to: SQL Server 2014 Service Pack 2SQL Server 2014 EnterpriseSQL Server 2014 Express

This article describes cumulative update package 4 (build number: 12.0.5540.0) for Microsoft SQL Server 2014 Service Pack 2 (SP2) . This update contains fixes that were released after the release of SQL Server 2014 SP2.

Cumulative update

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

Only the most recent CU that was released for SQL Server 2014 SP2 is available at the Download Center.
  • Each new CU contains all the fixes that were included with the previous CU for the installed version/Service Pack of SQL Server.
  • 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 2014 service pack .

How to obtain this cumulative update package

The following update is available from the Microsoft Download Center:

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 2014 SP2, this CU can be located and downloaded from the Microsoft Windows Update Catalog. However, Microsoft recommends that you install the latest cumulative update available.

Known Issue

After installing this CU, Change Data Capture (CDC) functionality might break if :

  • The databases enabled for CDC are part of Always On availability group (or)
  • SQL Server replication components are not installed on the server

For more information, see:

Additional hotfixes that are included in this cumulative update package

VSTS bug numberKB article numberDescriptionFix areaStatus
92373443205935 FIX: Error 2809 when you execute a stored procedure that takes a table-valued parameter from RPC calls in SQL Server 2014SQL performance
92373103067968 FIX: Memory is paged out when columnstore index query consumes lots of memory in SQL Server 2014SQL service
92908294010162FIX: A system assert occurs when a Transact-SQL stored procedure with a TVP argument is called from a SQLCLR procedureSQL service
90974783212318 Cannot set database to partial containment if the database was ever a part of change tracking SQL service
92372973030352FIX: The change table is ordered incorrectly for updated rows after you enable change data capture for a Microsoft SQL Server 2012 or 2014 database SQL service
92222284010344FIX: The sp_msx_enlist stored procedure fails to enlist a target server into a master server in SQL Server 2014 if the server name is too longManagement Tools
92373203208244 FIX: Access Violation when you execute queries on a readable secondary replica of a SQL Server 2014 AlwaysOn Availability Group SQL performance
93678203045321 MS15-058: Description of the security update for SQL Server 2012 Service Pack 2 GDR: July 14, 2015Reporting Services
93678513206912 FIX: Credential settings are lost when you schedule data refresh for PowerPivot workbooks Analysis Services
93682603211304 FIX: Error 5262 when you execute DBCC CHECKDB on the primary replica that contains repaired data pages in SQL Server 2012 or 2014High Availability
92886073213703 FIX: An Always On secondary replica goes into a disconnecting state High Availability
92373603208179 FIX: MDX query returns errors if the value of MaxRolapOrConditions is greater than 256 in SQL Server 2014 Analysis ServicesAnalysis Services
88508503159748 FIX: Cannot connect to a named instance after failover on a mirror server in SQL Server 2016 or 2014SQL connectivity
92954343212214FIX: Fails to execute the DBCC CLONEDATABASE command on an in-place upgrade instance of SQL Server SQL service
92373153196877 FIX: Incremental statistics runs with higher sample rate than regular statistics when statistics are created or updated in SQL Server 2014SQL performance
92373383208245 FIX: Incorrect query result when you use varchar(max) variable in the search condition in SQL Server 2014SQL performance
90062684010500FIX: Sys.dm_tran_commit_table DMV and CHANGETABLE function return incorrect results if SQL Server shuts down unexpectedlySQL service
92272844010159FIX: "Invoke-sqlcmd" cmdlet executes a query statement multiple times if an error occurs in SQL Server 2014Management Tools
93678163212193 FIX: Cannot save the SSRS report after you change a parameter in Report Builder or the SQL Server Data Tool Reporting Services
93678603025408 FIX: Access violation occurs when you run and then cancel a query on distinct count partitions in SSAS Analysis Services
93678253213240 FIX: Changing the data type and then updating the table with more than 4,000 records causes database corruptionSQL service
89813274009839FIX: An MDX query returns incorrect results in SSAS 2014 Tabular modeAnalysis Services
92373493209442 FIX: "No Data Available" in the SQL Server Memory Usage page in the SQL Server 2014 MDM reportManagement Tools
93166864010710 FIX: Memory leak occurs when you run a query that you don't have enough permissions in SQL Server 2014 SQL security
93255794010990 FIX: SQL Server is stopped when you install patches on an instance of SQL Server 2014 that contains many databases Setup & Install

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 hotfixes:

Cumulative update package information


To apply this cumulative update package, you must be running SQL Server 2014 SP2.

Restart information

You may have to restart the computer after you apply this cumulative update package.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.