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

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.
• 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).

Cumulative update information

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: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:

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: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:

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:

To alleviate this issue, decrease the number of primary databases that are merged on the secondary server.

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.

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.