Running DBCC DBREINDEX Statement Causes SQL Server 200 Sysindexes.statblob Column Corruption
Submitted By:
jimmyread
Rating:
(Not rated) (
Rate It)
Share:
By Email
Visit
Description
Are you one of those people whose database index tables got corrupted in SQL Server and made use of DBCC DBREINDEX T-SQL command to rebuild it? Due to such kind of thing, the data on the server becomes inaccessible and no matter how hard one tries it would be next to impossible to access them. This further result in data loss and in order to resolve such an odd behavior of MS SQL Server, one needs to make use of any good 3rd party sql database recovery software.
When the DBCC DBREINDEX T-SQL command is used on SQL Server 2000, there are chances that the Sysindexes.statblob column can get corrupted. There are some instances under which such a thing can occur and they are summarized under the following headings:
? In reference table is of indexed view
? Auto create statistics option enabled
? More than 1 index assigned for some columns
? Table in reference is a computed column
After running the aforesaid command, users can come across the following error messages popping up in front of their computer monitor:
? Server: Msg 2576, Level 16, State 1, Line 2 IAM page (0:0) is pointed to by the previous pointer of IAM page (1:88) object ID 1977058079 index ID 2 but was not detected in the scan.
? Server: Msg 8964, Level 16, State 1, Line 2 Table error: Object ID 2. The text, ntext, or image node at page (1:64), slot 29, text ID 6815744 is not referenced.
The corruption is so violent that it can certainly damage the master database files as well. The reason being SQL Server makes use of the Sysindexes.statblob column to store the entire column statistics and the image data stores all the data in a histogram format. When the MDF files get damaged, there would be no way around with the help of which they can access the data stored on the server. SQL Database Recovery is a very good application tool that helps in repairing and recovering all the corrupted items on server and making the inaccessible data accessible to you. It is easy to use and works with all the versions of SQL Server like 2000, 2002, 2003 and 2007.
Comments (0)
Add Your Rating
