Note This build number of this cumulative update package is 11.0.2332.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 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 hotfixes are now multilingual. 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.
- When you install the Cumulative update package 3 for SQL Server 2012, following statement on the "SQL Server 2012 Update" page is incorrect:
"This installation provides updates for SQL Server 2012 Community Technology Preview (August CTP)".
This statement should read as follows:
“This installation provides updates for SQL Server 2012”
Note Microsoft has confirmed that this is a problem with the installation package.
How to obtain Cumulative Update 3 for SQL Server 2012A 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, go to 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 in the following list, click the following article numbers to view the articles in the Microsoft Knowledge Base:
|VSTS bug number||KB article number||Description|
|930647||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|
|1017674||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|
|1017683||2645648||FIX: Export procedure fails when you export a 64-bit SSRS 2008 R2 report or a SSRS 2008 report that contains multiple levels of a document map to the PDF format|
|898888||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|
|969186||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|
|984792||2667742||FIX: "out of memory" error when you use ODBC with SQL Server 2012|
|934432||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|
|934424||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|
|969190||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|
|933038||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|
|969192||2699013||FIX: SQL Server 2012, SQL Server 2008 R2 or SQL Server 2008 stops responding and a "Non-yielding Scheduler" error is logged|
|927689||2703193||FIX: Incorrect results when you run a parallel query that uses a columnstore index in SQL Server 2012|
|969198||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|
|969200||2707015||FIX: rsInternalError error when you export a report that contains a Tablix control in SSRS 2008 R2 or in SSRS 2012|
|969202||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|
|969204||2708726||FIX: Performance Monitor .dll files in the system32 folder are not updated after you apply updates to SQL Server 2008 R2 or to SQL Server 2012|
|931285||2708786||FIX: Access violation when you try to build a columnstore index for a table in SQL Server 2012|
|931959||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|
|1017677||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|
|937512||2713827||FIX: "Dataflow - " error when you try to open an SSIS package in SSIS 2012|
|969210||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|
|937451||2714937||FIX: "No object exists with a lineage ID" error message when you run an SSIS 2012 package|
|969214||2715289||FIX: Incorrect results when you convert a datetimeoffset column to a smalldatetime column in SQL Server 2008 R2 or in SQL Server 2012 when there is an index on the datetimeoffset column|
|969212||2715312||FIX: Errors when you run a query that uses the FOR XML clause in the PATH mode in SQL Server 2008 R2 or in SQL Server 2012|
|958508||2718920||FIX: SQL Server Agent logs verbose logs in the Application log when you start a SQL Server 2012 failover cluster instance|
|976894||2725256||FIX: "Failure sending mail" error when you create a subscription to deliver an RDL report whose file name contains non-Latin characters in SSRS 2012|
|969463, 971495||2725950||FIX: Slow performance or deadlock when you restore a database and execute statements at the same time in SQL Server 2012|
|973290||2727221||FIX: You cannot install a SQL Server 2012 cluster instance on a Server Core operating system that contains an existing cluster instance|
|1017695||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|
|973758||2727824||"No such interface supported" error message when you add a project to a source control in SQL Server Management Studio 2012|
|983099||2731402||FIX: Incorrect email priority if you set the SSRS email subscription priority to Low or Normal in SSRS 2012|
|950921||2733091||FIX: SQL Server is slow or an "Out-Of-Memory" error occurs when you run a query with nested IF statements on DAX measures in SQL Server 2012|
|1010354||2735763||FIX: Execution of a package ends unexpectedly and status is "Canceled" when you execute many SSIS 2012 packages in parallel|
|968916||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|
|1011308||2740957||FIX: "FOR UPDATE clause allowed only for DECLARE CURSOR" error when you execute stored procedures together with cursor-specific syntax in SQL Server 2012|
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
ID do Artigo: 2723749 - Última Revisão: 19/11/2012 - Revisão: 1