- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsWe 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=30262
of row (class=0,object_id=1732957
in sys.sql_dependencies does not have a matching row (object_id=302624121,colum
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=30262
of row (class=0,object_id=2929121
in sys.sql_dependencies does not have a matching row (object_id=302624121,colum
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=30262
of row (class=0,object_id=3089121
in sys.sql_dependencies does not have a matching row (object_id=302624121,colum
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=30262
of row (class=0,object_id=1778821
in sys.sql_dependencies does not have a matching row (object_id=302624121,colum
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=78615
of row (class=0,object_id=1732957
in sys.sql_dependencies does not have a matching row (object_id=786153896,colum
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=10525
of row (class=0,object_id=1732957
in sys.sql_dependencies does not have a matching row (object_id=1052582838,colu
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=13162
of row (class=0,object_id=1732957
in sys.sql_dependencies does not have a matching row (object_id=1316251794,colu
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=13162
of row (class=0,object_id=1732957
in sys.sql_dependencies does not have a matching row (object_id=1316251794,colu
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=15882
of row (class=0,object_id=1732957
in sys.sql_dependencies does not have a matching row (object_id=1588252763,colu
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.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: kenhaleyPosted on 2007-07-25 at 14:54:28ID: 19570164
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.