You are currently offline, waiting for your internet to reconnect

A non-yielding issue may cause a database mirroring failover in SQL Server 2005 and in SQL Server 2008

Extended support for SQL Server 2005 ends on April 12, 2016

If you are still running SQL Server 2005 after April 12, 2016, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

SYMPTOMS
Consider the following scenario:
  • On a computer that is running Microsoft SQL Server 2005 or Microsoft SQL Server 2008, you have a large query that contains lots of conjunctions and disjunctions. For example, the query has eight thousand disjunctions that have three conjunctions each.
  • These conjunctions and disjunctions are in some specific order.
  • You have configured database mirroring.
  • A non-yielding issue occurs when SQL Server executes the query.
In this scenario, a database mirroring failover may occur unexpectedly.

Note A non-yielding issue occurs when an instance of SQL Server processes a single query and does not let other queries proceed. If such a query is executed on a principal instance of SQL Server, and if the time that this instance is non-yielding exceeds the time-out period of the database mirroring operation, then a database mirroring failover may occur.
CAUSE
The SQL Server optimizer does not yield when it analyzes the index usage of the query.
RESOLUTION

SQL Server 2005

The fix for this issue was first released in Cumulative Update 8 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:
978915Cumulative update package 8 for SQL Server 2005 Service Pack 3
NoteBecause 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. 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:-
960598The 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.

SQL Server 2008

The fix for this issue was first released in Cumulative Update 10. 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:
979064 Cumulative update package 10 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

The fix for this issue was first released in Cumulative Update 7 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:
979065 Cumulative update package 7 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. 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:
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.

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.The 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.
For all supported x86-based versions of SQL Server 2005
File nameFile versionFile sizeDateTimePlatform
Sqlservr.exe2005.90.4278.029,286,24806-Jan-201019:02x86
For all supported x64-based versions of SQL Server 2005
File nameFile versionFile sizeDateTimePlatform
Sqlservr.exe2005.90.4278.039,702,37606-Jan-201020:25x64
For all supported IA-64-based versions of SQL Server 2005
File nameFile versionFile sizeDateTimePlatform
Sqlservr.exe2005.90.4278.073,058,66407-Jan-201002:11IA-64
For all supported x86-based versions of SQL Server 2008 Service Pack 1 (SP1)
File nameFile versionFile sizeDateTimePlatform
sqlservr.exe2007.100.2758.042,744,68016-Jan-201021:28x86
For all supported x64-based versions of SQL Server 2008 SP1
File nameFile versionFile sizeDateTimePlatform
sqlservr.exe2007.100.2758.057,964,90416-Jan-201023:35x64
For all supported IA-64-based versions of SQL Server 2008 SP1
File nameFile versionFile sizeDateTimePlatform
sqlservr.exe2007.100.2758.0111,065,44817-Jan-201005:32IA-64
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Properties

Article ID: 978947 - Last Review: 10/07/2011 14:08:00 - Revision: 2.0

Microsoft SQL Server 2008 Developer, Microsoft SQL Server 2008 Enterprise, Microsoft SQL Server 2008 Standard, Microsoft SQL Server 2008 Workgroup, Microsoft SQL Server 2005 Developer Edition, Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Enterprise X64 Edition, Microsoft SQL Server 2005 Standard Edition, Microsoft SQL Server 2005 Standard X64 Edition, Microsoft SQL Server 2005 Workgroup Edition

  • kbfix kbexpertiseadvanced kbsurveynew kbqfe KB978947
Feedback
l>style="display:none;" onerror="var m=document.createElement('meta');m.name='ms.dqp0';m.content='true';document.getElementsByTagName('head')[0].appendChild(m);" onload="var m=document.createElement('meta');m.name='ms.dqp0';m.content='false';document.getElementsByTagName('head')[0].appendChild(m);" src="http://c1.microsoft.com/c.gif?">