FIX: Changes to Filtered Indexed View Can Cause Unexpected Results (306467)



The information in this article applies to:

  • Microsoft SQL Server 2000 Developer Edition SP1
  • Microsoft SQL Server 2000 Enterprise Edition SP1
  • Microsoft SQL Server 2000 Enterprise Evaluation Edition SP1

This article was previously published under Q306467
BUG #: 355069 (SHILOH_BUGS)

SYMPTOMS

If an indexed view is created and the view schema filters the results with a WHERE clause, future data modifications may cause unexpected results.

RESOLUTION

To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack

Hotfix

NOTE: The following hotfix was created prior to SQL Server 2000 Service Pack 2.

The English version of this fix should have the following file attributes or later:
   Version      Platform
   ---------------------
   s80436i.exe  x86
				
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

IMPORTANT: This fix will only prevent future occurrences of unexpected results due to data modifications; in addition to applying the fix, all indexes based on views with filter conditions need to be re-created.

WORKAROUND

Do not perform filtering in the schema for a view that will be indexed.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 2000 Service Pack 1.

This problem was first corrected in SQL Server 2000 Service Pack 2.

Modification Type:MajorLast Reviewed:11/14/2003
Keywords:kbbug kbfix kbQFE KB306467