FIX: Error message after you run the DBCC DBREINDEX Transact-SQL statement on a table that does not have a unique clustered index on a SQL Server 2005-based computer: "Msg 2511"

Consider the following scenario:

• On a Microsoft SQL Server 2005-based computer, you have a table that does not have a unique clustered index.
• You run the DBCC DBREINDEX Transact-SQL statement on the table.

In this scenario, you may receive the following error message when you run the DBCC CHECKDB Transact-SQL statement on the computer:

This issue occurs because a bad execution plan for the DBCC DBREINDEX Transact-SQL statement uses an optimization that causes the incorrect order to be run. Therefore, the index of the table is corrupted.

The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: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. 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:Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

To work around this issue, use the ALTER INDEX Transact-SQL statement to rebuild the index instead of using the DBCC DBREINDEX Transact-SQL statement.

For more information about the ALTER INDEX Transact-SQL statement, visit the following Microsoft Developer Network (MSDN) Web site:For more information about the DBCC DBREINDEX Transact-SQL statement, visit the following MSDN Web site:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site: 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:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: