Select the product you need help with
FIX: In SQL Server 2008 or in SQL Server 2005, the session that runs the TRUNCATE TABLE statement may stop responding, and you cannot end the sessionArticle ID: 954831 - View products that this article applies to. Bug #:
50003005 (SQL Hotfix) Bug#: 50003320 (SQL Hotfix) SQL Server 2008Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.SQL Server 2005Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
For more information about the master list of builds that were released after SQL was released, click the following article number to view the article in the Microsoft Knowledge Base:
957826
(http://support.microsoft.com/kb/957826/
)
Where you can find more information about the SQL Server 2008 builds that were released after SQL Server 2008 and the SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2
On This PageSUMMARYThis article describes the following about this hotfix
release:
SYMPTOMSTo remove all the rows from a temporary table in Microsoft SQL Server 2008 or in Microsoft SQL Server 2005, you run the TRUNCATE TABLE statement. When you do this, the session
that runs the TRUNCATE TABLE statement may stop responding. Additionally,
you cannot end the session. When
this problem occurs, the following error message is logged in the SQL Server
error log: <Date>
<Time> spid10s OBJECT: 2:434475576:0 CleanCnt:3 Mode:Sch-M
Flags: 0x0 <Date> <Time> spid10s Grant List 1: <Date> <Time> spid10s Owner:0x0000000003D9D980 Mode: Sch-M Flg:0x0 Ref:1 Life:02000000 SPID:813 ECID:0 XactLockInfo: 0x00000005CB3C8C08 <Date> <Time> spid10s Requested By: <Date> <Time> spid10s ResType:LockOwner Stype:'OR'Xdes:0x00000002765EB450 Mode: Sch-M SPID:813 BatchID:0 ECID:0 TaskProxy:(0x00000003764BC410) Value:0x5123900 Cost:(N/A) <Date> <Time> spid10s Deadlock monitor failed to resolve this deadlock. Server may require restart to recover from this condition <Date> <Time> spid10s Using 'dbghelp.dll' version '4.0.5' <Date> <Time> spid10s **Dump thread - spid = 10, PSS = 0x0000000082046B60, EC = 0x0000000082046B70 <Date> <Time> spid10s ***Stack Dump being sent to C:\Microsoft SQL Server 2005\MSSQL.1\MSSQL\LOG\SQLDump0001.txt <Date> <Time> spid10s * ******************************************************************************* <Date> <Time> spid10s * <Date> <Time> spid10s * BEGIN STACK DUMP: <Date> <Time> spid10s * <Date> <Time> spid 10 <Date> <Time> spid10s * <Date> <Time> spid10s * Unresolved deadlock <Date> <Time> spid10s * <Date> <Time> spid10s * <Date> <Time> spid10s * ******************************************************************************* <Date> <Time> spid10s * ------------------------------------------------------------------------------- <Date> <Time> spid10s * Short Stack Dump <Date> <Time> spid10s Stack Signature for the dump is 0x0000000000000283 <Date> <Time> spid10s Timeout waiting for external dump process 5256. CAUSEThis problem occurs because of a deadlock. Each temporary table has an in-memory structure that contains a counter of all the pending transactions that operated on the table. When this counter decreases to 0, the temporary table is dropped in an autonomous transaction. However, the TRUNCATE TABLE statement does not increase the counter. Therefore, if the autonomous transaction tries to drop the temporary table before the transaction that runs the TRUNCATE TABLE statement commits, a deadlock occurs. The deadlock occurs between the autonomous transaction and the transaction that runs the TRUNCATE TABLE statement. Typically, SQL Server internally resolves the deadlock. However, SQL Server cannot resolve the deadlock in some cases. Therefore, the session in which the transaction runs stops responding, and you cannot end the session. RESOLUTIONSQL Server 2008The fix for this issue was first released in Cumulative Update 1.For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base: 956717 Note 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 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix.
(http://support.microsoft.com/kb/956717/
)
Cumulative update package 1 for SQL Server 2008
For more information, click the following article number to view the article in the Microsoft Knowledge Base: 956909
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was released
SQL Server 2005Cumulative update informationThe fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:953752 Note 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 2005 fix release. Microsoft recommends 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:
(http://support.microsoft.com/kb/953752/LN/
)
Cumulative update package 9 for SQL Server 2005 Service Pack 2937137 Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix 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 hotfix. Note If additional issues occur or if 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 hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for
which the hotfix is available. If you do not see your language, it is because a
hotfix is not available for that language.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, you must have SQL Server 2005 Service Pack 2 installed. For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:913089
(http://support.microsoft.com/kb/913089/
)
How to obtain the latest service
pack for SQL Server 2005
Restart informationYou do not have to restart the computer after you apply this hotfix.Registry informationYou do not have to change the registry.Hotfix file informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.SQL Server 2005 32-bit versionCollapse this table
SQL Server 2005 x64-based versionCollapse this table
SQL Server 2005 Itanium architecture versionCollapse this table
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. MORE INFORMATIONSQL Server 2008For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:956717
(http://support.microsoft.com/kb/956717/LN/
)
Cumulative update package 1 for SQL Server 2008SQL Server 2005For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:953752
(http://support.microsoft.com/kb/953752/LN/
)
Cumulative update package 9 for
SQL Server 2005 Service Pack 2REFERENCESSQL Server 2008For more information about the list of builds that are available after the release of SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:956909 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:
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was released
935897 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:
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
822499 For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesSQL Server 2005For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:937137 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:
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
935897 For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/935897/LN/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems913089 For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:
(http://support.microsoft.com/kb/913089/LN/
)
How to obtain the latest service pack for SQL Server 2005 http://go.microsoft.com/fwlink/?LinkId=71711 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:
(http://go.microsoft.com/fwlink/?LinkId=71711)
822499 For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/LN/
)
New naming schema for Microsoft SQL Server software update packages824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 954831 - Last Review: September 19, 2008 - Revision: 3.0 APPLIES TO
|
Back to the top
