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 |
|
bogey
Posting Yak Master
166 Posts |
 Posted - 2007-05-22 : 09:10:43
|
| I'm getting the following error when running dbcc checkdb and no clue as to what to do.Msg 8992, Level 16, State 1, Line 1Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=1328111872,referenced_minor_id=5) of row (class=0,object_id=1795589535,column_id=0,referenced_major_id=1328111872,referenced_minor_id=5) in sys.sql_dependencies does not have a matching row (object_id=1328111872,column_id=5) in sys.columns. |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2007-05-22 : 11:05:31
|
| This is saying that an object (probably an SP) has a missing column description in sys.columns.Was this database upgraded from 2000 recently? Could be that someone deleted something from the system tables before the upgrade.If not, I don't know what could cause this apart from:1) a bug2) someone deleting something from the system tables directly in 2005 (hard to do but can be done)3) a corruption (although I'd expect to see more errors from CHECKDB in that case)This can't be repaired by CHECKDB (it won't repair metadata). You'll need to restore from a backup or drop/recreate the affected object.ThanksPaul RandalPrincipal Lead Program Manager, Microsoft SQL Server Core Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)http://blogs.msdn.com/sqlserverstorageengine/default.aspx |
 |
|
|
bogey
Posting Yak Master
166 Posts |
Posted - 2007-05-22 : 14:56:02
|
| Database was upgraded from 2000. |
|
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2007-05-23 : 10:41:33
|
| So when was the last time CHECKDB was run cleanly? Before or after the upgrade? My guess is that this occured on the 2000 system and hasn't been noticed until now.Paul RandalPrincipal Lead Program Manager, Microsoft SQL Server Core Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)http://blogs.msdn.com/sqlserverstorageengine/default.aspx |
|
|
|
gigiduru
Starting Member
3 Posts |
Posted - 2009-03-27 : 03:51:31
|
quote:
Originally posted by paulrandal
So when was the last time CHECKDB was run cleanly? Before or after the upgrade? My guess is that this occured on the 2000 system and hasn't been noticed until now.Paul RandalPrincipal Lead Program Manager, Microsoft SQL Server Core Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)http://blogs.msdn.com/sqlserverstorageengine/default.aspx
Hi Paul,I am experiencing the same error on a database migrated (through backup restore) from SQL2000 SP4 to SQL2005 SP2.DBCC CHECKDB was run on a daily basis on SQL2000 without any issues reported. As soon as the databasewasrestored on 2005, I got these errors reported...Any clues...?Thanks in advance. |
|
|
|
gigiduru
Starting Member
3 Posts |
Posted - 2009-03-27 : 06:48:59
|
quote:
Originally posted by gigiduru
quote:
Originally posted by paulrandal
So when was the last time CHECKDB was run cleanly? Before or after the upgrade? My guess is that this occured on the 2000 system and hasn't been noticed until now.Paul RandalPrincipal Lead Program Manager, Microsoft SQL Server Core Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)http://blogs.msdn.com/sqlserverstorageengine/default.aspx
Hi Paul,I am experiencing the same error on a database migrated (through backup restore) from SQL2000 SP4 to SQL2005 SP2.DBCC CHECKDB was run on a daily basis on SQL2000 without any issues reported. As soon as the databasewasrestored on 2005, I got these errors reported...Any clues...?Thanks in advance.
OK, sorry for the fuss... I found the explanation.By analyzing each object involved in the errors, I found that there were several stored procedures that were referencing unexistent columns of tables (that no longer had those columns of course)... after having modified/dropped the SPs the errors were gone. |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-03-29 : 03:21:06
|
quote:
Originally posted by gigiduru
DBCC CHECKDB was run on a daily basis on SQL2000 without any issues reported. As soon as the databasewasrestored on 2005, I got these errors reported...
No surprise there. On 2000, checkdb did not run checkcatalog so this kind of problem often went completely unnoticed. On 2005/2008, checkDB does run checkcatalog and hence the problems show up.--Gail ShawSQL Server MVP |
|
|
|
|
|
|
|
|
sys.sql_dependencies does not have a matching row