Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: Deadlocks may occur when multiple concurrent query notification subscriptions are fired on same objects in SQL Server 2005 or in SQL Server 2008

FIX: Deadlocks may occur when multiple concurrent query notification subscriptions are fired on same objects in SQL Server 2005 or in SQL Server 2008

Microsoft 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.Microsoft 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.

↑ Back to the top

Symptoms

Consider the following scenario:
  • In Microsoft SQL Server 2005 or in Microsoft SQL Server 2008, you set up multiple query notification subscriptions on some tables.
  • You update these tables.
  • The requests for the query notification subscriptions are fired concurrently.
In this scenario, deadlocks may occur on the query notification system tables (for example, a system table with a name that resembles sys.query_notification_xxxxxx). Additionally, the following deadlock graph is logged in the SQL Server error log file:
waiter id=process7f8dc48 mode=U requestType=wait,
waiter-list,
owner id=process873ce38 mode=U,
owner-list,
keylock hobtid=72057594049462272 dbid=5 objectname=<Database>.sys.query_notification_626101271 indexname=cidx id=lock178dd6c0
mode=U associatedObjectId=72057594049462272,

waiter id=process873ce38 mode=U requestType=wait,

waiter-list,

owner id=process7f8dc48 mode=U,
owner-list,
keylock hobtid=72057594049462272 dbid=5 objectname=<Database>.sys.query_notification_626101271 indexname=cidx id=lock176848c0
mode=U associatedObjectId=72057594049462272,
resource-list,
<Query>,
inputbuf,
<Query>,
frame procname=adhoc line=1 sqlhandle=0x020000009f5c4302918e8370f6d9bd71045a53f75b8056b3,
executionStack,
process id=process873ce38 taskpriority=0 logused=0 waitresource=KEY: 5:72057594049462272 (0e0086ec58d5) waittime=4984 ownerId=574444809 transactionname=CQueryScan::BeginNotifXact lasttranstarted=<Date><Time> XDES=0x732047f8 lockMode=U schedulerid=7 kpid=8068 status=suspended spid=133 sbid=0 ecid=0 priority=0 transcount=0 lastbatchstarted=<Date><Time> lastbatchcompleted=<Date><Time> clientapp=.Net SqlClient Data Provider hostname=<hostname> hostpid=1824 loginname=<loginname> isolationlevel=read committed (2) xactid=574444808 currentdb=5 lockTimeout=4294967295 clientoption1=671088672 clientoption2=128056,

<Query>,
inputbuf,
<Query>,
frame procname=adhoc line=1 sqlhandle=0x020000009f5c4302918e8370f6d9bd71045a53f75b8056b3,
executionStack,
process id=process7f8dc48 taskpriority=0 logused=0 waitresource=KEY: 5:72057594049462272 (0d006843edc7) waittime=4984 ownerId=574444769 transactionname=CQueryScan::BeginNotifXact lasttranstarted=<Date><Time> XDES=0x6adc9528 lockMode=U schedulerid=5 kpid=676 status=suspended spid=293 sbid=0 ecid=0 priority=0 transcount=0 lastbatchstarted=<Date><Time> lastbatchcompleted=<Date><Time> clientapp=.Net SqlClient Data Provider hostname=<hostname>110 hostpid=1272 loginname=<loginname> isolationlevel=read committed (2) xactid=574444768 currentdb=5 lockTimeout=4294967295 clientoption1=671088672 clientoption2=128056,

process-list,
deadlock victim=process873ce38,
deadlock-list,

↑ Back to the top

Cause

By default, SQL Server uses the READ_COMMITTED transaction isolation level. Therefore, SQL Server's internal queries have potential to run into deadlocks. In the scenario that is described in the "Symptoms" section, the queries that cause the deadlock are internal queries.

↑ Back to the top

Resolution

SQL Server 2005 Service Pack 3


The fix for this issue was first released in Cumulative Update 6 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
974648 Cumulative update package 6 for SQL Server 2005 Service Pack 3
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:
960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

The release version of SQL Server 2008

Important You must install this fix if you are running the release version of SQL Server 2008.

The fix for this issue was first released in Cumulative Update 8. 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:
975976 Cumulative update package 8 for SQL Server 2008
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. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released

SQL Server 2008 Service Pack 1

Important You must install this fix if you are running SQL Server 2008 Service Pack 1.


The fix for this issue was first released in Cumulative Update 5 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
975977 Cumulative update package 5 for SQL Server 2008 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 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:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.


After you apply this fix, the isolation level will be set to Serializable when database engine accesses the system tables.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

According to the cause of this problem, the typical method of tuning and indexing cannot resolve this issue. The hotfix is used to temporarily modify the isolation level to a higher level for a certain part of this transaction to make sure the problematic queries do not run into deadlock.

↑ Back to the top

References

For more informationabout the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems

For more informationabout how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

 For more information about the new features in SQL Server 2005 Service Pack 3 (SP3) and about the improvements in SQL Server 2005 SP3, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=131442
For more informationabout the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

 For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kb, kbfix, kbqfe, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 975090
Revision : 6
Created on : 9/29/2020
Published on : 9/29/2020
Exists online : False
Views : 300