Note This build number of this cumulative update package is 11.0.3321.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 1 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|
|1086784||2406666||FIX: "[Teradata Database] " error when you click "Count" in the Aggregation Design Wizard in SSAS 2008, in SSAS 2012 or in SSAS 2008 R2|
|1078523||2445812||FIX: A column that uses the DATETIME data type does not replicate to an Oracle subscriber by using a transactional replication in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012|
|1078647||2644794||FIX: fFalse assertion error when you try to convert the value from an XML column to an XML variable in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012|
|1078655||2645648||FIX: Export procedure fails when you export a 64-bit SSRS 2008 R2 report, SSRS 2012 report or a SSRS 2008 report that contains multiple levels of a document map to the PDF format|
|1078512||2651629||FIX: Error message when you use DTA to tune one or more queries against a database that contains many objects in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012|
|1086762||2661644||FIX: Access violation in the sqlservr!ReplicaToPrimaryPageCopier::ReadIoCompletionRoutine function in SQL Server 2008 R2 or in SQL Server 2012|
|1078579||2667037||FIX: "The connection string format is not valid" error when you try to create a maintenance plan for a SQL Server 2008 R2 or SQL Server 2012 server|
|1078631||2667742||FIX: "out of memory" error when you use ODBC with SQL Server 2012, SQL Server 2008 R2 or SQL Server 2008|
|1078541||2671078||FIX: "Attempting to set a non-NULL-able column's value to NULL" error message when you use a MERGE statement in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012|
|1086761||2671318||FIX: The first execution of the xp_cmdshell stored procedure is not completed until the last execution is complete in SQL Server 2012|
|1078538||2680799||FIX: Error message when you perform a full population of a full-text index by using word breakers for Chinese language in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012|
|1078582||2697983||FIX: An incorrect value is stored in the TIME_ZONE column of the BACKUPSET table in SQL Server 2008 R2 or in SQL Server 2012|
|1078535||2698639||FIX: Performance of a SELECT statement that contains a LIKE operator and an ESCAPE clause is low in SQL Server 2008 R2 or in SQL Server 2012|
|1078588||2699013||FIX: SQL Server 2012, SQL Server 2008 R2 or SQL Server 2008 stops responding and a "Non-yielding Scheduler" error is logged|
|1078516||2703193||FIX: Incorrect results when you run a parallel query that uses a columnstore index in SQL Server 2012|
|1078593||2706601||FIX: Series groups in a report are missing when you render the report in SQL Server 2008 Reporting Services or in later versions of Reporting Services|
|1078597||2708027||FIX: "An error has occurred during report processing" error message when you try to preview an SSRS 2008 R2 or SSRS 2012 report after you set the dataset collation to Greek or Greek_100|
|1078527||2708786||FIX: Access violation when you try to build a columnstore index for a table in SQL Server 2012|
|1078530||2709075||"A severe error occurred on the current command" error when you run a full-text query that has the CONTAINS predicate in SQL Server 2012|
|1078649||2713151||FIX: Access violation when you use Database Engine Tuning Advisor to tune a table in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012 if you enable the "Include filtered indexes" check box|
|1078547||2713827||FIX: "Dataflow - " error when you try to open an SSIS package in SSIS 2012|
|1078603, 1086774||2714634||FIX: SQL Server 2008 R2 or SQL Server 2012 takes a long time to generate scripts for a partitioned table that uses the data compression feature|
|1078544||2714937||FIX: "No object exists with a lineage ID" error message when you run an SSIS 2012 package|
|1078573||2720171||FIX: Error message when you run an SSIS package if the sys.xp_regread stored procedure is revoked in SQL Server 2012: "The EXECUTE permission was denied on the object 'xp_regread'"|
|1086770||2723979||FIX: Access violation in SQL Server internal deadlock monitor when you run multiple applications together with Multiple Active Result Sets enabled in SQL Server 2008 R2 or in SQL Server 2012|
|1078613, 1078616||2725950||FIX: Slow performance or deadlock when you restore a database and execute statements at the same time in SQL Server 2012|
|1078658||2727322||FIX: Incorrect results are returned when you run a query that uses parallelism in the query execution plan in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012|
|1086769||2728419||FIX: "Tuning process exited unexpectedly" error message when you run Database Engine Tuning Advisor under the db_owner role in SQL Server 2008 R2 or in SQL Server 2012|
|1086771||2728534||FIX: "A system assertion check has failed" error when you re-create a nonclustered index on a column in SQL Server 2008 R2 or in SQL Server 2012|
|1086773||2731068||FIX: "An unexpected error occurred" when you query some calculation data of an SSAS tabular model by using SQL Server 2008 R2 PowerPivot for Excel 2010 or SQL Server 2008 R2 PowerPivot for SharePoint 2010|
|1086772||2737499||FIX: KeepTogether property does not work when you generate a report that contains a tablix in SSRS 2008 R2 or in SSRS 2012|
|1078575||2737580||FIX: Internal error when you execute queries against a non-rectangular mining model by using DMX or MDX in SQL Server 2012 Analysis Services|
|1086766||2738197||FIX: Worker threads do not wake up immediately when multiple I/O-intensive tasks are running at the same in SQL Server 2012|
|1086767||2739940||FIX: Database is offline and in "In Recovery" state when you rebuild an index in SQL Server 2012 if the transaction log is full|
|1086780||2752511||FIX: "Arithmetic overflow error" message when you run the sys.sp_tables_info_90_rowset_64 system stored procedure on a linked server in SQL Server 2012|
|1086781||2754444||FIX: "Index and length must refer to a location within the string" error message when you extract a large volume of data from SAP BW in an SSIS 2012 package|
|1086782||2754939||FIX: Access violation occurs when you run a full-text query in SQL Server 2012|
|1086785||2755079||FIX: Changes are not synchronized to subscribers after you change an article filter in a transactional replication publication in SQL Server 2008, in SQL Server 2012 or in SQL Server 2008 R2|
|1086763||2756097||FIX: "Community Technology Preview (August CTP)" is displayed in the installation or uninstallation wizard of a SQL Server 2012 update|
|1086765||2762557||FIX: "Process appears to be non-yielding on Scheduler " error message when you run a query in SQL Server 2012|
|1086783||2762559||FIX: SQL Server 2012 failures are displayed in the Task Status Notifications dialog box in System Center Operations Manager 2012|
|1086786||2762593||FIX: Tablediff utility reports incorrect results when a table contains a primary key in a uniqueidentifier column in SQL Server 2012|
|1115973||2780716||FIX: Data loss when you export Microsoft Azure SQL Database to a data-tier application .bacpac package|
|1116032||2780719||FIX: Data loss when you import a data-tier application from a .bacpac package file to Microsoft Azure SQL Database|
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
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