This article describes cumulative update package 2 (Build number: 12.0.2370.0) for Microsoft SQL Server 2014. This update contains hotfixes for issues that were fixed after the release of SQL Server 2014.
Click "Hotfix Download Available" at the top of this Knowledge Base article. If the "Hotfix Request" page doesn't appear, contact Microsoft Customer Service and Support to obtain the cumulative update package.
|VSTS bug number||KB article number||Description||Fix area|
|2320904||2926223||FIX: Performance problems occur in NUMA environments during foreign page processing in SQL Server 2012 or SQL Server 2014||Management Tools|
|2525263||2928300||FIX: Intense query compilation workload does not scale with growing number of cores on NUMA hardware and results in CPU saturation in SQL Server||SQL performance|
|2577481||2931815||FIX: Loads or queries on CCI tables block one another in SQL Server 2014||SQL service|
|2525268||2932559||FIX: Totals are wrong after you filter on a pivot table item and remove the filter in SSAS 2012 or SSAS 2014||Analysis Services|
|2357157||2933103||FIX: Assertion failure when you execute a query specifying TOP N and ORDER BY in SQL Server||SQL performance|
|2357159||2936154||FIX: DTA utility crashes with an access violation when you use user-defined function in SQL Server||Management Tools|
|2525272||2938192||FIX: The execution of SSIS package takes a long time when you cannot enable garbage collector server mode in SSIS 2012 or SSIS 2014||Integration Services|
|2357155||2938476||FIX: Errors when you use export/import data wizard to move data in SQL Server||Integration Services|
|2525274||2939277||FIX: Incorrect results when you run queries that contain UNION operator by using parallel query plan in SQL Server||SQL performance|
|2356245||2950189||FIX: An access violation occurs when you execute update query on a table that has a DML trigger in SQL Server||SQL performance|
|2525282||2950209||FIX: Access violation when the start offset is larger than the string length in Substring function in SQL Server||SQL service|
|2525284||2952101||FIX: Poor cardinality estimation when the ascending key column is branded as stationary in SQL Server||SQL performance|
|2356249||2953354||FIX: Log Reader Agent fails when you have Oracle Publishing configured in SQL Server||SQL service|
|2525270||2954480||FIX: SSAS instance crashes when you perform writeback action by using the role with cell security defined||Analysis Services|
|2578298||2956619||FIX: The execution of an SSIS package that is stored in MSDB is slower than it is stored on the file system||Integration Services|
|2525286||2958062||FIX: Error 515 when you add a subscription and then delete it in SQL Server 2012 or SQL Server 2014||SQL service|
|2525279||2960237||FIX: Error when you execute DQS stored procedure [internal_core].[RestoreDQDatabases] in SQL Server||Data Quality Services (DQS)|
|2578300||2960310||FIX: Access violation when you maintain RBS with the .NET Framework 4.0 in related configuration file in SQL Server||SQL service|
|2525301||2960735||FIX: Windows Update for SQL Server 2012 or SQL Server 2014 image does not work in Windows Azure Virtual Machine gallery||Setup & Install|
|2525295||2960989||FIX: Error when you use DQS Cleansing component with large batch in an SSIS 2012 or SSIS 2014 package||DQS|
|2525290||2961254||FIX: The execution of an MDX query in SSAS 2012 or SSAS 2014 is much slower than it is in SSAS 2008 R2||Analysis Services|
|2323206||2961258||FIX: Cannot access the data in FileTable after you upgrade from SQL Server 2012 SP1 to SQL Server 2014||SQL service|
|2525299||2962650||FIX: Access violation occurs when running a Process Recalc on a tabular table in SSAS 2012 or SSAS 2014||Analysis Services|
|2556603||2963408||FIX: Error 5180 occurs when you query BLOB column data in SQL Server||SQL service|
|2403053||2966096||FIX: Access violation when you insert data into a table that has a clustered columnstore index in SQL Server 2014||SQL service|
|2452407||2967198||FIX: DBCC SHRINKDATABASE or DBCC SHRINKFILE cannot move pages that belong to the nonclustered columnstore index||SQL service|
|2525261||2967240||FIX: Cannot reclaim unused space by using shrink operation in the table that contains a LOB column in SQL Server||SQL service|
|2525266||2967634||FIX: SSIS 2012 or SSIS 2014 XML validator only outputs "TRUE" or "FALSE" when you perform XML validation||Integration Services|
|2593575||2967900||FIX: Data models do not load after you run a PowerPivot scheduled data refresh job when you work with SQL Server 2014||Analysis Services|
|2307220||2968023||FIX: Error in checking master database after you bind a memory-optimized database to a resource pool in SQL Server 2014||In-Memory OLTP|
|2505083||2968627||FIX: Dump file and deadlock when you run update and CTAS with limited log space in SQL Server 2014 PDW V2 AU1||SQL service|
|2505028||2968658||FIX: Latch time-out when you insert data into the CCI on an AlwaysOn secondary site in SQL Server 2014||SQL service|
|2262840||2968974||FIX: You cannot create a power view report against a UDM cube in SSAS 2014||Analysis Services|
|2525689||2969419||FIX: Truncated CCI partitioned table runs for a long time in SQL Server 2014||SQL service|
|2525699||2969421||FIX: Poor performance when you bulk insert into partitioned CCI in SQL Server 2014||SQL service|
|2467130||2969741||FIX: Sys.indexes returns incorrect value for indexes in SQL Server 2014||In-Memory OLTP|
|2516201||2969781||FIX: Error when you add a custom connection manager in SSIS 2014 Designer||Integration Services|
| 2685532||2969896||FIX: Data loss in clustered index occurs when you run online build index in SQL Server 2012 or SQL Server 2014||SQL service|
|2415675||2970137||FIX: Instance ID is different in related system tables after you register a database as a DAC in SQL Server 2014||Management Tools|
|2551005||2970386||FIX: Metadata corruption occurs when you update index statistics with INCREMENTAL=ON in SQL Server 2014||SQL performance|
|2612142||2973444||FIX: "SQL Server performance counters are disabled" when you move the SQL Server resource in SQL Server 2014||Reporting Services|
|2262877||2974373||FIX: Poor performance when you use DAX functions on a String or Boolean column in SSAS 2014||Analysis Services|
|2370041||2974374||FIX: Cloud Adapter crashes when you restore a database on a Windows Azure virtual machine deployed by using a SQL Server 2014 image||Management Tools|
|2531344||2974376||FIX: Error when you execute a stored procedure that inserts records into temp table the second time in SQL Server 2014||SQL service|
|2505065||2974397||FIX: Error when you drop a clustered columnstore index table during recovery in SQL Server 2014||SQL service|
|2505092||2974398||FIX: "Possible termination due to exception during stack unwinding" error during exception handling in SQL Server 2014||SQL service|
|2361316||2962599||Can now disable checking whether dimension and partition data originate from the same data source when you run a ROLAP query in SQL Server 2014||Analysis Services|
- We recommend that you test hotfixes before you deploy them in a production environment.
- We recommend that you apply the most recent update release .
- This cumulative package is intended to correct only the problems that are described in this article. Apply it only to systems that are experiencing these specific problems.
- The most recent update release contains all the hotfixes and all the updates that were included with the previous SQL Server 2014 update release.
- We recommend that you upgrade your SQL Server to the next SQL Server 2014 service pack .
Hybrid environments deployment
When you deploy the hotfixes to a hybrid environment (Such as AlwaysOn, replication, cluster, mirroring, and cluster), we recommend that you go and refer to the following articles before you deploy them:
- SQL Server failover cluster rolling update and service pack process.
If you do not want to use the rolling update process, follow these steps in order to apply a CU or SP:
- Install the service pack on the passive node.
- Install the service pack on the active node (This step requests service restart).
- Upgrade and update of availability group servers that use minimal downtime and data loss.
If you enabled AlwaysOn with SSISDB catalog for additional considerations about how to apply a CU or SP in these environments, go and see the article from the following MSDN blog:
- How to apply a hotfix for SQL Server in a transactional replication and database mirroring topology
- How to apply a hotfix for SQL Server in a replication topology
- How to install service packs and hotfixes on an instance of SQL Server that is configured to use database mirroring
- Overview of SQL Server Servicing Installation
PrerequisitesTo apply this cumulative update package, you must be running SQL Server 2014.
Restart informationYou may have to restart the computer after you apply this cumulative update package.
Registry informationTo use one of the hotfixes in this package, you do not have to make any changes to the registry.
- How to obtain the latest service pack for SQL Server 2014.
- The Incremental Servicing Model for SQL Server to deliver hotfixes for reported problems.
- Naming schema for Microsoft SQL Server software update packages.
- Description of the standard terminology that is used to describe Microsoft software updates.
Article ID: 2967546 - Last Review: 17 Apr 2015 - Revision: 1