Cumulative Update 11 for SQL Server 2014 SP1

Applies to: SQL Server 2014 DeveloperSQL Server 2014 StandardSQL Server 2014 Enterprise Core

This article describes cumulative update package 11 (build number: 12.0.4502.0) for Microsoft SQL Server 2014 Service Pack 1 (SP1) . This update contains fixes that were released after the release of SQL Server 2014 SP1.

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

Hotfixes that are included in this cumulative update package

VSTS bug numberKB article numberDescriptionFix area
93678543213703 FIX: An Always On secondary replica goes into a disconnecting stateHigh Availability
85391083208276 Update improves handling of documents too large for Full-Text Search indexing in SQL Server 2014SQL service
93678403203693“A digitally signed driver is required” warning when you install SQL Server packages in Windows Server 2016 and Windows 10SQL service
88508493159748 FIX: Cannot connect to a named instance after failover on a mirror server in SQL Server 2016SQL connectivity
93682563211304 FIX: Error 5262 when you execute DBCC CHECKDB on the primary replica that contains repaired data pages in SQL Server 2012High Availability
91330074009823FIX: AFTER DELETE triggers occur in the wrong order in the ON DELETE CASCADE action chain in SQL Server 2014SQL performance
93678113192692 FIX: Assert memory dump on a mirror server in SQL Server 2012High Availability
93678153212193 FIX: Cannot save the SSRS report after you change a parameter in Report Builder or the SQL Server Data ToolReporting Services
93678193045321 MS15-058: Description of the security update for SQL Server 2012 Service Pack 2 GDR: July 14, 2015Reporting Services
93678503206912 FIX: Credential settings are lost when you schedule data refresh for PowerPivot workbooksAnalysis Services
93678343207327 FIX: On failover, the new secondary replica stops accepting transaction log records until the instance is restarted in SQL ServerHigh Availability
93678583025408 FIX: Access violation occurs when you run and then cancel a query on distinct count partitions in SSASAnalysis Services
93678233213240 FIX: Changing the data type and then updating the table with more than 4,000 records causes database corruptionSQL service
4009839 FIX: MDX query returns incorrect result in SSAS 2014 Tabular modeMaster Data Service

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 SP1.

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.