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 |
|
gavis
Starting Member
39 Posts |
 Posted - 2009-06-12 : 06:02:54
|
| hi i get this error when i run a dbcc checkdbany help will be appreciated |
|
|
tosscrosby
Aged Yak Warrior
676 Posts |
Posted - 2009-06-12 : 09:42:11
|
| Run DBCC CheckDB dbname with ALL_ERRORMSGS and post the resultsTerry-- Procrastinate now! |
 |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-06-12 : 10:15:58
|
Also the No_INFOMSGS option is useful to remove the informational messages that are of no interest in corruption cases. DBCC CHECKDB (< Database Name > ) WITH NO_INFOMSGS, ALL_ERRORMSGS Do you have a clean backup of this database?--Gail ShawSQL Server MVP |
|
|
|
gavis
Starting Member
39 Posts |
Posted - 2009-06-12 : 10:29:18
|
| hi terryhere is the message.msg 8966, level 16could not read and latch page (1:954) with latch type SH. sysindexes failed.please contact you system administrator. |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-06-12 : 14:13:15
|
| Do you have a backup?You've got irreparable corruption there. CheckDB cannot and will not attempt to fix the system tables. Take a look at this article. [url]http://www.sqlservercentral.com/articles/65804/[/url] There's a section towards the bottom on how to 'fix' irreparable corruption. Your options are limited. You can restore a clean backup or you can script out what you can, bcp out what data you can and create a new database.--Gail ShawSQL Server MVP |
|
|
|
gavis
Starting Member
39 Posts |
Posted - 2009-06-13 : 02:31:12
|
| hi.great feedback, i did restored and imported missing data between the two databases.Thanks Again-- |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-06-13 : 07:08:59
|
| Glad you got it sorted.--Gail ShawSQL Server MVP |
|
|
|
|
|
|
could not read and latch page (1:954) with latch t