Table of contents
×

This article describes cumulative update package 3 (Build number: 12.0.4427.24) for Microsoft SQL Server 2014 Service Pack 1 (SP1). This update contains hotfixes for issues that were fixed after the release of SQL Server 2014 SP1.

How to get this cumulative update package

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.

Hotfixes that are included in this cumulative update package

VSTS bug number

KB article number

Description

Fix area

5618976

3092704

Improvements for Distribution Agent telemetry for Azure subscribers are available in SQL Server 2014

SQL service

5666744

3094865

FIX: "The process could not initialize '

SQL service

5704512

3096617

FIX: Can’t backup in-memory OLTP database that is restored by using full and differential restore in SQL Server 2014

In-Memory OLTP

5575649

3097073

FIX: CPU usage is higher than expected when you reduce the value of CAP_CPU_PERCENT argument in creating resource pool

SQL service

5544313

3097970

FIX: Sp_describe_undeclared_parameters returns incorrect result when undeclared parameter targets a decimal column

SQL service

5181922

3068359

FIX: "Cannot find the OLAP cube Model" error when you update the pivot table in a SharePoint document in SQL Server 2012 or SQL Server 2014

Analysis Services

5181941

3066299

FIX: Non-English items display in the MDS Explorer when you set language settings for web browser to English

Master Data Services (MDS)

5715080

3087114

FIX: PowerPivot for SharePoint doesn't run automatic data refresh on the first day of each month

Analysis Services

5715082

3088307

FIX: Scheduler deadlock on primary replica when you remove a replica from an AlwaysOn availability group in SQL Server 2012 or SQL Server 2014

High Availability

5715087

3077273

FIX: Rare incorrect result occurs when you run parallel query in SQL Server 2012 or SQL Server 2014

SQL service

5715090

3080209

FIX: Error 602 when you run a stored procedure repeatedly in SQL Server 2012 or SQL Server 2014

SQL performance

5715112

3080856

FIX: Information disclosure when you create a session cube by using dynamic role-based security in SQL Server 2012 or SQL Server 2014

Analysis Services

5715123

3089687

FIX: Can't export empty Tablix header in CSV file when NoHeader is false in SSRS 2012 or SSRS 2014

Reporting Services

5715131

3087872

FIX: Access violations when you use the FileTable feature in SQL Server 2012 or SQL Server 2014

SQL service

5715193

3097114

FIX: Queries take longer time to compile in SQL Server 2014 than in earlier versions

SQL performance

4745298

3035737

FIX: SSAS instance crashes when cube writeback commit transaction and processing batch are executed at the same time

Analysis Services

5489704

3099487

FIX: 100% CPU usage occurs when in-memory OLTP database is in recovery state in SQL Server 2014

In-Memory OLTP

5687518

3095958

FIX: Metadata inconsistency error occurs after you switch table partitions and drop corresponding files and filegroups

SQL service

5808923

3099323

FIX: DBCC CHECKFILEGROUP reports false inconsistency errors on database that has partitioned table in SQL Server 2014

SQL service

5667070

3096400

FIX: It takes longer to run the ALTER DATABASE SET HADR OFF command on a secondary replica in SQL Server 2014

High Availability

5181949

3075669

FIX: SSAS 2012 or SSAS 2014 crashes when you execute an MDX query that contains lots of Union expressions

Analysis Services

5181961

3073530

FIX: Access Violation error occurs when you run DDL SQL statements on a database in an instance of SQL Server 2012 or SQL Server 2014

Analysis Services

5181966

3073907

FIX: SSIS 2012 or SSIS 2014 package with an Execute SQL Task may stop responding

Analysis Services

5715073

3095156

FIX: Error 9002 and error 3052 when you try to add or back up log file in SQL Server 2012 or SQL Server 2014

High Availability

5715100

3081580

FIX: "String or binary data would be truncated" error when you use peer-to-peer replication in SQL Server 2012 or SQL Server 2014

SQL service

5715108

3087094

FIX: It takes longer than expected when you run a query with non-admin user role in SSAS 2012 or SSAS 2014 in Tabular model

Analysis Services

5715110

3088480

FIX: Sort operator spills to tempdb in SQL Server 2012 or SQL Server 2014 when estimated number of rows and row size are correct

SQL performance

5522017

2682488

FIX: Backup operation fails in a SQL Server database after you enable change tracking

SQL service

5536023

3090141

FIX: Offline checkpoint thread shuts down without providing detailed exception information in SQL Server 2014

In-Memory OLTP

5523582

3072814

FIX: Access violation occurs when you connect to an instance of SQL Server by using sqlcmd utility in SQL Server 2014

SQL connectivity

5523590

3080155

FIX: Rare index corruption when you build a columnstore index with parallelism on a partitioned table in SQL Server 2014

SQL service

5523599

3082860

FIX: Access violation occurs when you execute a query that contains many joins and coalesce functions in SQL Server 2014

SQL performance

5523600

3082005

FIX: Case-sensitive does not work in MDS database in SQL Server 2014

MDS

5715102

3091643

FIX: Error occurs when you configure SQL Server replication or set up a linked server in SQL Server 2012 or SQL Server 2014

SQL security

5829179

3100361

FIX: DBCC CHECKDB doesn't report metadata inconsistency of invalid filegroups in its summary in SQL Server 2014

SQL service

5038265

3092702

FIX: It takes a longer time than earlier versions of SQL Server when you run DBCC CHECKDB in SQL Server 2012

SQL service

5285700

321185

This update introduces a new global property that exposes the latest CU number that is currently installed on the SQL Server. After you install this update, you can obtain the CU number information by executing either of the following queries:

SELECT @@VERSION
SELECT SERVERPROPERTY('PRODUCTUPDATELEVEL')

Additionally, this update also adds the CU number information to the first line of the SQL Server error log.
For more information, review Methods 2 through Method 4 under the section How to determine which version and edition of SQL Server Database Engine is running in How to determine the version and edition of SQL Server and its components.



Need more help?

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

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×