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

How to obtain 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

3524159

3009974

FIX: Slow AG synchronization when disks have different sector sizes for primary and secondary replica log files in SQL Server 2012

SQL service

2369445

2793580

FIX: An update enables you to exclude system databases from Query Statistics collection sets when you use the management data warehouse in SQL Server

Management Tools

3074321

2840657

FIX: Performance decreases when you stage many records in MDS for SQL Server 2012

SQL service

3029598

2994082

FIX: Error when you edit models for some groups or users in SQL Server 2012 MDS

Data Quality Services (DQS)

3053494

2995352

FIX: "No catalog entry found for partition ID

SQL service

3127645

2997020

FIX: "An item with the same key has already been added" error when you review a report in SSRS 2012

Reporting Services

3047505

2998870

FIX: "The record ID is incorrect" error when you use DAX to execute query in a parent/child dimension in SSAS 2012

Analysis Services

3242852

3000494

The slides of a PowerPoint file that is exported from a PowerView report show blank when you open it in slider show mode

Reporting Services

3153124

3005300

FIX: High CPU consumption when you use spatial data type and associated methods in SQL Server 2012

SQL service

3158657

3008000

FIX: Error when you use Microsoft Office 15.0 Access Database Engine OLE DB Provider as data source in SSMS 2012

Integration Services

3443831

3013551

FIX: SQL Server is in script upgrade mode for a long time after you apply a SQL Server hotfix or security update

SQL service

Need more help?

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

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×