Microsoft KB Archive/905765

= FIX: A view is corrupted after you run the DBCC DBREINDEX Transact-SQL statement to rebuild the clustered index on a view in SQL Server 2000 =

Article ID: 905765

Article Last Modified on 2/14/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 64-bit Edition
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Developer Edition

-



Bug #: 474652 (SQL Server 8.0)



Notice
''Microsoft distributes Microsoft SQL Server 2000 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 2000 fix release.''



This article describes the following about this hotfix release:
 * The issues that are fixed by this hotfix package
 * The prerequisites for installing the hotfix package
 * Information about whether you must restart the computer after you install the hotfix package
 * Information about whether the hotfix package is replaced by any other hotfix package
 * Information about whether you must make any registry changes
 * The files that are contained in the hotfix package



SYMPTOMS
Consider the following scenario. You have an instance of SQL Server 2000 that runs on a multiprocessor computer. Additionally, you set the value of the max degree of parallelism option to a number that differs from 1. You do this to use several processors for parallel plan execution. You run the DBCC DBREINDEX Transact-SQL statement to rebuild the clustered index on a view. In this scenario, the view is corrupted. If you run the DBCC CHECKTABLE Transact-SQL statement on the view, you receive error messages that are similar to the following:

Server: MSN 8951, Level 16, State 1, Line 1 Table error:

Table ‘TableName’ (ID 1354896575). Missing or invalid key in index ‘IndexName’ (ID 2) for the row

Server: Msg 8955, Level 16, State 1, Line 1 Data row identified by (RID =  OGUID =   and OAGUID =   and OAVGUID =   and OAVSGUID =  ) has index values (OAGUID =   and OAVEffectiveDate =   and OAVCredentialGUID =  ...

Note  and   represent the actual time and globally unique identifiers (GUID) of the error message.



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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.

Prerequisites

 * The Microsoft SQL Server 2000 Service Pack 3 (SP3) version of this hotfix requires SQL Server 2000 SP3 and baseline hotfix 8.00.1007.
 * The Microsoft SQL Server 2000 Service Pack 4 (SP4) version of this hotfix requires SQL Server 2000 SP4.

For more information about how to obtain SQL Server 2000 Service Pack 3 and SQL Server 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:

290211 How to obtain the latest SQL Server 2000 service pack

For more information about how to obtain SQL Server 2000 hotfix build 2000.80.1007, click the following article number to view the article in the Microsoft Knowledge Base:

893312 FIX: You may receive a &quot;SQL Server could not spawn process_loginread thread&quot; error message, and a memory leak may occur when you cancel a remote query in SQL Server 2000

Restart information
You do not have to restart the computer after you apply this hotfix

Registry information
You do not have to change the registry.

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

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 tool in Control Panel.

Microsoft SQL Server 2000 SP3 and baseline hotfix 8.00.1007 based hotfix
SQL Server 2000 32-bit version

SQL Server 2000 Itanium architecture version

Microsoft SQL Server 2000 SP4 based hotfix
SQL Server 2000 32-bit version

SQL Server 2000 Itanium architecture version



WORKAROUND
To work around this problem, drop the clustered index on the view, re-create the clustered index on the view, and then re-create the non-clustered indexes on the view.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
Before you run the DBCC DBREINDEX Transact-SQL statement to rebuild the clustered index on a view, you can set the value of the max degree of parallelism option to 1. When you do this, you avoid the problem that is mentioned in the &quot;Symptoms&quot; section. After the DBCC DBREINDEX Transact-SQL statement executes successfully, set the value of the max degree of parallelism option back to the number that was originally set.

For more information about the naming schema for Microsoft 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

