FIX: A query returns an incorrect result if it uses an index that is being rebuilt online in SQL Server 2005, SQL Server 2008 R2 or SQL Server 2008

Article ID: 981713 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2005, Microsoft SQL Server 2008 R2 or 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 2005, Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2008 fix release.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • In Microsoft SQL Server 2005, Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2008, you have a local partitioned view.
  • You perform an online index rebuild operation on an index that belongs to one of the partitions.
  • You run a query that uses the index that is being rebuilt.
In this scenario, you receive an incorrect result when you run the query.

When this problem occurs, if you run the "DBCC CHECKTABLE('<Table>') WITH NO_INFOMSGS, All_ERRORMSGS" command, you receive error messages that resemble the following:
Msg 8952, Level 16, State 1, Line <LineNumber>
Table error: table '<Table>' (ID <TableID>). Index row in index '<Index>' (ID <IndexID>) does not match any data row. Possible extra or invalid keys for:
Msg 8956, Level 16, State 1, Line <LineNumber>
Index row (<file_id>:<page_no>:<row_no>) with values (<IndexColumn> = '<Value>' and <OtherColumn> = <Value> and <OtherColumn> = <Value>) pointing to the data row identified by (<OtherColumn> = <Value> and <OtherColumn> = <Value>)
Msg 8951, Level 16, State 1, Line <LineNumber>
Table error: table '<Table>' (ID <TableID>). Data row does not have a matching index row in the index '<Index>' (ID <IndexID>). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line <LineNumber>
Data row (<file_id>:<page_no>:<row_no>) identified by (<OtherColumn> = <Value> and <OtherColumn> = <Value>) with index values <IndexColumn> = '<Value>' and <OtherColumn> = <Value> and <OtherColumn> = <Value>.
Back to the top | Give Feedback

CAUSE

This problem occurs because SQL Server 2005, SQL Server 2008 R2 or SQL Server 2008 does not use the correct query plan when there is a concurrent online index build operation for the partitioned view.
Back to the top | Give Feedback

RESOLUTION

Cumulative update information



SQL Server 2005

The fix for this issue was first released in Cumulative Update 9 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:
980176
(http://support.microsoft.com/kb/980176/LN/ )
Cumulative update package 9 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. 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:
960598
(http://support.microsoft.com/kb/960598/LN/ )
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.

SQL Server 2008 Service Pack 1

The fix for this issue was first released in Cumulative Update 9 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:
2083921
(http://support.microsoft.com/kb/2083921/LN/ )
cumulative update 9 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
(http://support.microsoft.com/kb/970365/LN/ )
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.

SQL Server 2008 Service Pack 2

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

SQL Server 2008 R2


The 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 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2072493
(http://support.microsoft.com/kb/2072493/ )
Cumulative update package 2 for SQL Server 2008 R2
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:
981356
(http://support.microsoft.com/kb/981356/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

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.
Back to the top | Give Feedback

REFERENCES

For more information about partitioned views, visit the following Microsoft Developer Network (MSDN) Web site:
Using partitioned views
(http://msdn.microsoft.com/en-us/library/ms190019(SQL.90).aspx)


For more information about how online index operations work, visit the following Microsoft MSDN Web site:
How online index operations work
(http://msdn.microsoft.com/en-us/library/ms191261(v=SQL.90).aspx)
For information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897
(http://support.microsoft.com/kb/935897/ )
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
913089
(http://support.microsoft.com/kb/913089/ )
How to obtain the latest service pack for SQL Server 2005
For more information about new features and improvements in SQL Server 2005 Service Pack 3, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=131442
(http://go.microsoft.com/fwlink/?LinkId=131442)
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:
822499
(http://support.microsoft.com/kb/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
(http://support.microsoft.com/kb/824684/ )
Description of the standard terminology that is used to describe Microsoft software updates
Back to the top | Give Feedback

Properties

Article ID: 981713 - Last Review: November 15, 2010 - Revision: 5.0
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Workgroup
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Workgroup
Keywords: 
kbexpertiseadvanced kbsurveynew kbfix kbqfe KB981713
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top