Article ID: 905765 - Last Review: February 14, 2007 - Revision: 1.5 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
Bug #: 474652 (SQL Server 8.0) NoticeMicrosoft 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:
SYMPTOMSConsider 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 (Time) identified by (RID = (Time) OGUID = GUID and OAGUID = GUID and OAVGUID = GUID and OAVSGUID = GUID) has index values (OAGUID = GUID and OAVEffectiveDate = Time and OAVCredentialGUID = GUID... RESOLUTION A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.Prerequisites
290211
(http://support.microsoft.com/kb/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
(http://support.microsoft.com/kb/893312/
)
FIX: You may receive a "SQL Server could not spawn process_loginread thread" error message, and a memory leak may occur when you cancel a remote query in SQL Server 2000
Restart informationYou do not have to restart the computer after you apply this hotfixRegistry informationYou do not have to change the registry.Hotfix file informationThis 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 hotfixSQL Server 2000 32-bit versionCollapse this table
Collapse this table
Microsoft SQL Server 2000 SP4 based hotfixSQL Server 2000 32-bit versionCollapse this table
Collapse this table
WORKAROUNDTo 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. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONBefore 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 "Symptoms" 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
(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
REFERENCESFor more information about the max degree of parallelism option, visit the following Microsoft Developer Network (MSDN) Web site: http://msdn2.microsoft.com/en-us/library/aa196725(SQL.80).aspx
(http://msdn2.microsoft.com/en-us/library/aa196725(SQL.80).aspx)
For more information about the DBCC DBREINDEX Transact-SQL statement, visit the following MSDN Web site: http://msdn2.microsoft.com/en-us/library/aa258828(SQL.80).aspx
(http://msdn2.microsoft.com/en-us/library/aa258828(SQL.80).aspx)
For more information about the DBCC CHECKTABLE Transact-SQL statement, visit the following MSDN Web site: http://msdn2.microsoft.com/en-us/library/aa258646(SQL.80).aspx
(http://msdn2.microsoft.com/en-us/library/aa258646(SQL.80).aspx)
| Article Translations
|
Back to the top
