Note This build number of this cumulative update package is 11.0.3339.0.
We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 SP1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Important notes about the cumulative update package
- SQL Server 2012 SP1 hotfixes are now multilanguage. Therefore, there is only one cumulative hotfix package for all languages.
- One cumulative hotfix package includes all the component packages. The cumulative update package updates only those components that are installed on the system.
How to obtain Cumulative Update 2 for SQL Server 2012 SP1A supported cumulative update package is now available from Microsoft. However, it is intended to correct only the problems that are described in this article. Apply it only to systems that are experiencing these specific problems. This cumulative update package may receive additional testing. Therefore, if you are not severely affected by any of these problems, we recommend that you wait for the next SQL Server 2012 service pack that contains the hotfixes in this cumulative update package.
If the cumulative update is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the cumulative update package.
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific cumulative update package. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
Hotfixes that are included in this cumulative update package
Microsoft Knowledge Base articles that discuss these hotfixes will be released as they become available.
For more information about the SQL Server bugs, click the following article numbers to view the articles in the Microsoft Knowledge Base:
|VSTS bug number||KB article number||Description|
|1155749||972936||FIX: "SqlDumpExceptionHandler: Process generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION." error when you run a query in SQL Server 2012, in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2005|
|1133945||2509302||A database transaction log continues to grow after you upgrade to SQL Server 2012, SQL Server 2008 R2 SP1, SQL Server 2008 SP2 or SQL Server 2008 SP3|
|1154924||2674636||FIX: The size of a database file is not reduced when you use the DBCC SHRINKFILE command in SQL Server 2008 R2 or in SQL Server 2012|
|1029028||2688395||FIX: Cannot create a snapshot of a database that contains a full-text catalog in read-only or standby mode in SQL Server 2012|
|1133924||2696161||FIX: Error message when you try to view a report in SSRS 2012, in SSRS 2008 R2 or in SSRS 2008: "Different query parameters resulted in a same hash"|
|1154926||2715512||FIX: Error messages when you use dtexec to execute packages in SSIS 2008, in SSIS 2012 or in SSIS 2008 R2|
|1136154||2715841||FIX: Report Viewer 2010 does not display the DateTime parameter when you run a report in SSRS 2012|
|1155739||2734191||FIX: Reports are not printed in the defined page size when you use the RSClientPrint control to print reports in SSRS 2008 R2|
|1080478||2739213||FIX: Error message when you render an SSRS report that uses the rc:Toolbar=false parameter in the URL: "An error occurred within the report server database"|
|1154934||2742131||"0xe0434f4d" exception and "0xC001000A" error message when you create a maintenance plan on an MSX server|
|1034257||2748780||FIX: Calculated measures are changed after you browse a cube in SSAS 2012|
|1080464||2749913||FIX: Unhandled exception when you use a marked transaction that spans multiple databases in SQL Server 2008 R2 or in SQL Server 2012|
|1080488||2752432||FIX: High CPU usage when you query a binary large object column by using the NOLOCK hint in SQL Server 2008 R2 or in SQL Server 2012|
|1080467||2754301||FIX: Large queries that modify data run slower than expected when many locks accumulate in a SQL Server 2008 R2 or in SQL Server 2012|
|1080470||2754800||FIX: Error 17066 when you replicate a table article that contains an ntext data type column in SQL Server 2008 R2 or in SQL Server 2012|
|1080490||2755767||FIX: A transaction log restore operation takes longer than expected and a 3402 error occurs if a database file is removed in SQL Server 2008 R2 or in SQL Server 2012|
|1133929||2756471||FIX: Incorrect result is returned when you query an indexed view by using the NOEXPAND hint in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012|
|1080476||2757356||FIX: "The component is waiting for a notification" error message and SSIS 2012 or SSIS 2008 R2 package stops responding when you use Microsoft Connector 1.1 for SAP BI to extract data from SAP BW|
|1080458||2761600||FIX: Text is truncated in a Tablix control in an report of SSRS 2008 R2 or SQL Server 2012 after you export the report as a PDF or image file|
|1133941||2761934||Support for the varchar(max), nvarchar(max), and varbinary(max) data types is added in most OLE DB providers in SQL Server 2012 or in SQL Server 2008 or in SQL Server 2008 R2|
|1080492||2762102||FIX: Incorrect result when you run an MDX query that has an Aggregate function in SSAS 2008 R2 or in SSAS 2012|
|1158568||2765785||FIX: Access violation when you execute an SSIS 2008 R2 or SSIS 2012 package that contains a Sort transformation on a computer that has multiple CPUs|
|1154928||2767183||FIX: Installation failure when you try to install SQL Server 2012 Remote Blob Store for an additional database on the same instance of SQL Server by using the command line|
|1154929||2769594||SQL Server 2012 experiences out-of-memory errors|
|1154930||2769673||FIX: Data type length is doubled in a generated script when you use the SQL Server 2012 Change Data Capture Service for Oracle by Attunity|
|1158570||2770258||FIX: You receive an incorrect result when you run a query against a partitioned table in SQL Server 2008 R2 or in SQL Server 2012|
|1158572||2776344||FIX: Deadlocks occur when you execute a stored procedure to alter a temporary table if lock partitioning is enabled in SQL Server 2008 R2 or in SQL Server 2012|
|1154933||2776947||FIX: Incorrect result in a calculated column when the column contains an expression that resembles "ISBLANK(RELATED())" in SSAS 2012|
|1154936||2777097||FIX: Defined measure groups for a perspective are missing after you save or deploy the perspective in Visual Studio|
|1133954||2778088||FIX: Memory leak if you enable the AUTO_UPDATE_STATISTICS_ASYNC statistics option in SQL Server 2008, in SQL Server 2012 or in SQL Server 2008 R2|
|1154937||2778200||A hotfix is available that improves performance for an MDX query that uses the "NON EMPTY" operation together with overlapping calculations in SQL Server 2012 Analysis Services|
|1158574||2778479||FIX: 17066 and 3624 errors when you run the sp_refreshview stored procedure in a large batch that performs binary large object-related operations in SQL Server 2008 R2 or in SQL Server 2012|
|1101725||2778494||FIX: Incorrect result when you run a query that uses the TRY_CONVERT function together with the style parameter in SQL Server 2012|
|1154931||2779898||FIX: Error messages when you impersonate another user and run an MDX query in SSAS 2012|
|1158580||2781008||FIX: "User cannot be found" error message in SSRS 2008 R2 or in SSRS 2012 after the logon name is changed in Active Directory|
|1122125||2781126||FIX: W3wp.exe exceptions and SharePoint farm becomes unavailable after you disable a data refresh schedule for a PowerPivot workbook in SharePoint 2013 that interacts with SSAS 2012|
|1155752||2781486||FIX: Error messages when you perform a product update to a UCP-managed instance of SQL Server 2008 R2 or SQL Server 2012|
|1133338||2785014||FIX: Access violation when you split a partitioned table in SQL Server 2012|
|1133455||2785054||FIX: Incorrect results when a query references _90 Windows collations in SQL Server 2012|
|1158588||2785079||FIX: A "non-yielding" error occurs on a server for Service Broker Message Forwarding in SQL Server 2008 R2 or in SQL Server 2012|
|1154927||2785699||FIX: Error message when you view SharePoint integrated data-driven subscriptions after you upgrade to SSRS 2012|
|1155758||2786212||FIX: Access violation occurs when you run a spatial query over a linked server in SQL Server 2008 R2 or in SQL Server 2012|
|1158592||2788362||FIX: Error 28921 and error 18054 when you start an instance of SQL Server 2008 R2 or SQL Server 2012 that is upgraded from SQL Server 7.0|
|1143654||2790878||FIX: Error when you rerun a matching policy rule in a Data Quality Client application in SQL Server 2012|
|1138636||2792894||FIX: Error when you publish business rules for an entity in SQL Server 2012|
|1161356||2793634||Windows Installer starts repeatedly after you install SQL Server 2012 SP1|
|1140319||2800050||FIX: Component installation process fails after you install SQL Server 2012 SP1|
|1128676||2800293||FIX: MDS entity-based staging process does not update attribute values after you apply SQL Server 2012 SP1|
|1155994||2800355||FIX: Attribute value does not update during validation when two business rules update the same attribute to a certain value in SQL Server 2012 MDS|
|1141158||2801379||FIX: Error 17883 when you run a query on a server that has many CPUs and a large amount of memory in SQL Server 2012|
|2792921||Description of new features in Cumulative Update 2 for SQL Server 2012 SP1|
Cumulative update package information
You may have to restart the computer after you apply this cumulative update.
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
How to uninstall this cumulative update packageTo uninstall this cumulative update package, follow these steps:
- In Control Panel, open the Add or Remove Programs item.
Note If you are running Windows 7, open the Programs and Features item in Control Panel.
- Locate the entry that was installed by this cumulative update package.
- Right-click the entry, and then select Uninstall to remove the cumulative update package.
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
Naming schema for Microsoft SQL Server software update packages
Description of the standard terminology that is used to describe Microsoft software updates