Cumulative Update 12 for SQL Server 2014 SP1

Applies to: SQL Server 2014 EnterpriseSQL Server 2014 EnterpriseSQL Server 2014 Express

This article describes cumulative update package 12 (build 12.0.4511.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 2014 SP1, this CU can be located and downloaded from the Microsoft Windows Update Catalog. However, Microsoft recommends that you install the latest cumulative update available.
VSTS bug numberKB article numberDescriptionFix areaStatus
98138224014732FIX: A memory leak in SQLWEP causes the host process Wmiprvse.exe to crash in SQL Server 2012 or 2014SQL service
98138594014706FIX: Failed assertion and many access violation dump files after the sp_replcmds stored procedure is canceled in SQL Server 2012 or 2014SQL service
93792254013236FIX: Bad query plan created on secondary replicas after statistics updated via FULLSCAN option on primary replica in SQL Server 2012 or 2014High Availability
98138473210089GDR update package for SQL Server 2016 SP1Reporting Services
93005304016804FIX: Deadlocks occur in SSISDB when you run multiple SSIS packages in SQL Server 2014Integration Services
98138304014756FIX: SQL Server Profiler fails to obfuscate sp_setapprole when it's executed from a remote procedure call in SQL Server 2012 or 2014SQL service
98138634014738FIX: Error occurs when you drop a subscription by using a non-sysadmin account in SQL Server 2012 or 2014SQL service
98138264013111FIX: DMV sys.dm_hadr_availability_group_states displays "NOT_HEALTHY" in synchronization_health_desc column on secondary replicas in SQL Server 2012 or 2014High Availability
96273624016945FIX: "The custom resolver for this article requires OLEAUT32.DLL with a minimum version of 2.40.4276" error occurs when you use merge publication in SQL Server 2014SQL service
98138544014798Update reduces the execution frequency of the sp_MSsubscription_cleanup stored procedure in SQL Server 2012 or 2014SQL service
94788064016361FIX: Service Broker endpoint connections aren't closed after an availability group failover in SQL ServerSQL 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 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.