FIX: Deadlock might occur in sys.dm_database_encryption_keys DMV in SQL Server 2008 R2 or in SQL Server 2012 when you run log shipping from many databases to one secondary server

Article ID: 2550375 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 R2 or SQL Server 2012 update release.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You set up a log shipping environment that has many primary servers for primary databases and that has only one secondary server in Microsoft SQL Server 2008 R2 or in Microsoft SQL Server 2012.
  • One of the secondary databases on the secondary server is in single-user mode.
  • You try to run the log shipping from the primary servers to the secondary server.

In this scenario, a deadlock may occur in sys.dm_database_encryption_keys dynamic management view (DMV).

Back to the top | Give Feedback

Resolution

Cumulative update information

SQL Server 2012

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2703275
(http://support.microsoft.com/kb/2703275/LN/ )
Cumulative update package 2 for SQL Server 2012
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. 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:
2692828
(http://support.microsoft.com/kb/2692828/LN/ )
The SQL Server 2012 builds that were released after SQL Server 2012 was released
You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.

SQL Server 2008 R2

The fix for this issue was first released in cumulative update package 10. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2591746
(http://support.microsoft.com/kb/2591746/ )
Cumulative update package 10 for SQL Server 2008 R2
Note Because the builds are cumulative, each new update release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 R2 update release. We recommend that you consider applying the most recent update release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356
(http://support.microsoft.com/kb/981356/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2633146
(http://support.microsoft.com/kb/2633146/ )
Cumulative Update package 4 for SQL Server 2008 R2 Service Pack 1
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 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:
2567616
(http://support.microsoft.com/kb/2567616/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008


The fix for this issue was first released in Service Package 3. For more information about how to obtain this SQL Server 2008 Service Package 3, click the following article number to view the article in the Microsoft Knowledge Base:

968382
(http://support.microsoft.com/kb/968382/ )
How to obtain the latest service pack for SQL Server 2008

Service pack information for SQL Server 2008 R2

To resolve this problem, obtain the latest service pack for SQL Server 2008 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2527041
(http://support.microsoft.com/kb/2527041/ )
How to obtain the latest service pack for SQL Server 2008 R2
Back to the top | Give Feedback

Workaround

To alleviate this issue, decrease the number of primary databases that are merged on the secondary server.
Back to the top | Give Feedback

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in SQL Server 2008 R2 Service Pack 2 for SQL Server 2008 R2.
Back to the top | Give Feedback

More information

The following table provides more information about the products or the tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product against which the rule is evaluated.


Collapse this tableExpand this table
Rule softwareRule titleRule descriptionProduct versions against which the rule is evaluated
System Center AdvisorSQL Server missing update KB2550375 to prevent deadlock between log shipping jobsSystem Center Advisor determines whether this instance of SQL Server is used as a log shipping secondary for more than one database. Also, advisor checks the current build and version of SQL Server. If the current build of SQL Server is less than the fix build, advisor generates the alert about this issue. Review the details that are provided in the “Information Collected” section of the advisor alert, and apply the fix that is discussed in this article.SQL Server 2008
SQL Server 2008 R2




Back to the top | Give Feedback

Properties

Article ID: 2550375 - Last Review: November 19, 2012 - Revision: 6.0
Applies to
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise Evaluation
  • Microsoft SQL Server 2008 Express
  • Microsoft SQL Server 2008 Express with Advanced Services
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Express
  • Microsoft SQL Server 2008 R2 Express with Advanced Services
  • Microsoft SQL Server 2012 Developer
  • Microsoft SQL Server 2012 Enterprise
Keywords: 
kbtshoot kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2550375
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top