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.
| Author |
Topic |
|
steel
Posting Yak Master
107 Posts |
 Posted - 2008-04-19 : 13:23:59
|
| hi allits urgent really urgent please reply soonI am getting error in sysindexes when i run dbcc checkdb on a production db.the error is Server: Msg 8928, Level 16, State 1, Line 1please help me to remove thisall the options of dbcc checkdb as well as table are not helping me thanks in advance |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2008-04-19 : 13:30:43
|
| Try dropping and recreating the index.Hope you have recent backups.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2008-04-19 : 14:14:14
|
quote:
Originally posted by nr
Try dropping and recreating the index.Hope you have recent backups.
Huh? 8928 is an error reading a page in the clustered index of sysindexes. You can't drop and recreate indexes on critical system tables.Your only option to repair this database is to restore from backups. CHECKDB cannot repair this problem - see my blog post [url]http://www.sqlskills.com/blogs/paul/2007/11/16/CHECKDBFromEveryAngleCanCHECKDBRepairEverything.aspx[/url] for more info.If you don't have any backups then you'll need to create a new database with the same schema as the corrupt one, and then export as much data as you can into the new database.You should also do some root-cause analysis to determine why the corruption occured in the first place.Hope this helps!Paul RandalSQL Server MVP, Managing Director, SQLskills.com |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2008-04-19 : 16:01:41
|
| Sorry - thought the OP was saying there was a problem with an index not sysindexes. Must read more carefully.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
steel
Posting Yak Master
107 Posts |
Posted - 2008-04-24 : 06:05:44
|
quote:
Originally posted by paulrandal
quote:
Originally posted by nr
Try dropping and recreating the index.Hope you have recent backups.
Huh? 8928 is an error reading a page in the clustered index of sysindexes. You can't drop and recreate indexes on critical system tables.Your only option to repair this database is to restore from backups. CHECKDB cannot repair this problem - see my blog post [url]http://www.sqlskills.com/blogs/paul/2007/11/16/CHECKDBFromEveryAngleCanCHECKDBRepairEverything.aspx[/url] for more info.If you don't have any backups then you'll need to create a new database with the same schema as the corrupt one, and then export as much data as you can into the new database.You should also do some root-cause analysis to determine why the corruption occured in the first place.Hope this helps!Paul RandalSQL Server MVP, Managing Director, SQLskills.com
Thanks for ur help sirplease tell me the exact reason of the inconsistency. |
|
|
|
|
|
|
urgent really urgent dbcc