• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1155
  • Last Modified:

Migrated Integrity Check failing in SQL2005

We have Windows 2003 running on our servers and we upgraded our databases from SQL2000 to SQL2005 two weeks ago.  We migrated all of our maintenance plans at that time.  All seem to work but one: The integrity check.  We deleted the migrated plan and created one from scratch using SQL2005...it still failed.  I have tried researching the error and had no luck...here is the text from the error message:

Executing the query "DBCC CHECKDB WITH NO_INFOMSGS" failed with the following error:
"Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=302624121,referenced_minor_id=1)
      of row (class=0,object_id=173295727,column_id=0,referenced_major_id=302624121,referenced_minor_id=1)
      in sys.sql_dependencies does not have a matching row (object_id=302624121,column_id=1) in sys.columns.
 Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=302624121,referenced_minor_id=1)
      of row (class=0,object_id=292912115,column_id=0,referenced_major_id=302624121,referenced_minor_id=1)
      in sys.sql_dependencies does not have a matching row (object_id=302624121,column_id=1) in sys.columns.
 Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=302624121,referenced_minor_id=1)
      of row (class=0,object_id=308912172,column_id=0,referenced_major_id=302624121,referenced_minor_id=1)
      in sys.sql_dependencies does not have a matching row (object_id=302624121,column_id=1) in sys.columns.
 Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=302624121,referenced_minor_id=1)
      of row (class=0,object_id=1778821399,column_id=0,referenced_major_id=302624121,referenced_minor_id=1)
      in sys.sql_dependencies does not have a matching row (object_id=302624121,column_id=1) in sys.columns.
 Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=786153896,referenced_minor_id=1)
      of row (class=0,object_id=173295727,column_id=0,referenced_major_id=786153896,referenced_minor_id=1)
      in sys.sql_dependencies does not have a matching row (object_id=786153896,column_id=1) in sys.columns.
 Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=1052582838,referenced_minor_id=4)
      of row (class=0,object_id=173295727,column_id=0,referenced_major_id=1052582838,referenced_minor_id=4)
      in sys.sql_dependencies does not have a matching row (object_id=1052582838,column_id=4) in sys.columns.
 Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=1316251794,referenced_minor_id=12)
      of row (class=0,object_id=173295727,column_id=0,referenced_major_id=1316251794,referenced_minor_id=12)
      in sys.sql_dependencies does not have a matching row (object_id=1316251794,column_id=12) in sys.columns.
 Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=1316251794,referenced_minor_id=66)
      of row (class=0,object_id=173295727,column_id=0,referenced_major_id=1316251794,referenced_minor_id=66)
      in sys.sql_dependencies does not have a matching row (object_id=1316251794,column_id=66) in sys.columns.
 Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=1588252763,referenced_minor_id=2)
      of row (class=0,object_id=173295727,column_id=0,referenced_major_id=1588252763,referenced_minor_id=2)
      in sys.sql_dependencies does not have a matching row (object_id=1588252763,column_id=2) in sys.columns.

CHECKDB found 0 allocation errors and 9 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 9 consistency errors in database 'Comfort'.".

Possible failure reasons:
Problems with the query,
"ResultSet" property not set correctly,
parameters not set correctly,
or connection not established correctly.
0
randyrood
Asked:
randyrood
1 Solution
 
kenhaleyCommented:
It looks like the upgrade failed to delete some entries in sysdependencies, that were probably replaced by new entries.  I would back up the database, then put it in single-user mode and run

DBCC CHECKDB (0, REPAIR_REBUILD)

If that fails to clear the error then try

DBCC CHECKDB (0, REPAIR_ALLOW_DATA_LOSS)

which can result in data loss if the errors are in the tables themselves (as opposed to structures/other objects).  However, I doubt if you'll lose data, since this is a dependencies issue.  But that's why you backup before trying this.
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now