[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.
Question
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
8.2

Migrated Integrity Check failing in SQL2005

Asked by randyrood in SQL Server 2005, Windows 2003 Server, MS SQL Server

Tags: row, does, have

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.
[+][-]07/25/07 02:54 PM, ID: 19570164Accepted Solution

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

About this solution

Zones: SQL Server 2005, Windows 2003 Server, MS SQL Server
Tags: row, does, have
Sign Up Now!
Solution Provided By: kenhaley
Participating Experts: 1
Solution Grade: A
 
 
Loading Advertisement...
20091111-EE-VQP-92