Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 inconsistency in sysindexes

Author  Topic 

steel
Posting Yak Master

107 Posts

Posted - 2008-04-21 : 00:38:49
hi all
Is there any way to remove inconsistencies from sysindexes table. I have already used all the options of the checkdb as well as checktable but invain.
thanks in advance

tosscrosby
Aged Yak Warrior

676 Posts

Posted - 2008-04-21 : 14:18:48
What type of inconsistences? Post the results of the error log and maybe we can help.

Terry
Go to Top of Page

steel
Posting Yak Master

107 Posts

Posted - 2008-04-22 : 00:29:51
this is the result of checkdb statementy when applied on the database.


Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 1705115648 owned by data record identified by RID = (1:233:13) id = 158623608 and indid = 7.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:200979), slot 2, text ID 1705115648 is not referenced.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:200992), slot 2, text ID 1705115648 is referenced by page (1:233), slot 13, but was not seen in the scan.

CHECKDB found 0 allocation errors and 3 consistency errors in table 'sysindexes' (object ID 2).

Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-04-22 : 17:07:10
Post in Database corruption forum. Paul randal will give you good suggestion.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-04-22 : 17:12:35
I will move the thread to the proper forum. But you need to provide the entire output of DBCC CHECKDB for him to help.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2008-04-24 : 07:56:24
Try dropping the statistics on index 7 for object 158623608. The corruption is in the statistics blob for the index.

If that doesn't work, you could try dropping and recreating the non-clustered index.

One of these *should* work.

Paul Randal
SQL Server MVP, Managing Director, SQLskills.com
Go to Top of Page
   

- Advertisement -