Select the product you need help with
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 2012Article ID: 2776344 - View products that this article applies to. Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 2 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 R2 Service Pack 2 fix release. On This PageSymptomsConsider the following scenario:
CauseThis issue occurs because the two sessions that are used to execute the stored procedure try to obtain locks on the same temporary table object when lock partitioning is enabled. ResolutionCumulative update informationCumulative update 6 for SQL Server 2012The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:2728897 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 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:
(http://support.microsoft.com/kb/2728897/
)
Cumulative update package 6 for SQL Server 20122692828
(http://support.microsoft.com/kb/2692828 /
)
The SQL Server 2012 builds that were released after SQL Server 2012 was released Cumulative Update 2 for SQL Server 2012 SP1The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:2790947 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 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:
(http://support.microsoft.com/kb/2790947/
)
Cumulative update package 2 for SQL Server 2012
Service Pack 12772858
(http://support.microsoft.com/kb/2772858/
)
The SQL
Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was
releasedCumulative update 4 for SQL Server 2008 R2 SP2The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP 2, click the following article number to view the article in the Microsoft Knowledge Base:2777358 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 R2 SP 2 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:
(http://support.microsoft.com/kb/2777358/
)
Cumulative update package 4 for SQL Server 2008 R2 Service Pack 22730301
(http://support.microsoft.com/kb/2730301/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was releasedStatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. WorkaroundTo work around the issue, execute the stored procedure together with the WITH RECOMPILE query hint. ReferencesFor more information about the lock partitioning, go to the following MSDN website: General information about lock partitioning For more information the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
(http://msdn.microsoft.com/en-US/library/ms187504(v=sql.105).aspx)
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/
)
Naming schema for Microsoft SQL Server software update packages 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates PropertiesArticle ID: 2776344 - Last Review: February 18, 2013 - Revision: 6.0 Applies to
| Article Translations
 |
Back to the top
