February 25, 2010 at 3:21 am
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=879911983) of row (object_id=879911983,column_id=3) in sys.columns does not have a matching row (object_id=879911983) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3856, State 1: Attribute (xml_collection_id=49664) exists but should not for row (object_id=930243631,column_id=4) in sys.columns (system_type_id=167).
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=930243631) of row (object_id=930243631,column_id=4) in sys.columns does not have a matching row (object_id=930243631) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3858, State 1: The attribute (precision=202) of row (object_id=930243631,column_id=5) in sys.columns has an invalid value.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=930243631) of row (object_id=930243631,column_id=5) in sys.columns does not have a matching row (object_id=930243631) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=930243631) of row (object_id=930243631,column_id=6) in sys.columns does not have a matching row (object_id=930243631) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=930243631) of row (object_id=930243631,column_id=7) in sys.columns does not have a matching row (object_id=930243631) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=930243631) of row (object_id=930243631,column_id=8) in sys.columns does not have a matching row (object_id=930243631) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3856, State 1: Attribute (xml_collection_id=8585216) exists but should not for row (object_id=930243631,column_id=9) in sys.columns (system_type_id=56).
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=930243631) of row (object_id=930243631,column_id=9) in sys.columns does not have a matching row (object_id=930243631) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3858, State 1: The attribute (system_type_id=249) of row (object_id=930243631,column_id=10) in sys.columns has an invalid value.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=930243631) of row (object_id=930243631,column_id=10) in sys.columns does not have a matching row (object_id=930243631) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=930243631) of row (object_id=930243631,column_id=11) in sys.columns does not have a matching row (object_id=930243631) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=661808175) of row (object_id=661808175,column_id=4390924) in sys.columns does not have a matching row (object_id=661808175) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=930243631) of row (object_id=930243631,column_id=13) in sys.columns does not have a matching row (object_id=930243631) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=930243631) of row (object_id=930243631,column_id=14) in sys.columns does not have a matching row (object_id=930243631) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=930243631) of row (object_id=930243631,column_id=15) in sys.columns does not have a matching row (object_id=930243631) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=930243631) of row (object_id=930243631,column_id=16) in sys.columns does not have a matching row (object_id=930243631) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3858, State 1: The attribute (scale=194) of row (object_id=930243631,column_id=17) in sys.columns has an invalid value.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=930243631) of row (object_id=930243631,column_id=17) in sys.columns does not have a matching row (object_id=930243631) in sys.objects.
February 25, 2010 at 7:29 am
What does checkdb recommend for a repair level? If the repair level is REPAIR_ALLOW_DATA_LOSS you will need to find a good backup and restore from it and subsequent differential and log backups.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
February 25, 2010 at 7:31 am
Jack Corbett (2/25/2010)
What does checkdb recommend for a repair level?
None. Those errors are not repairable.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 25, 2010 at 7:32 am
GilaMonster (2/25/2010)
Jack Corbett (2/25/2010)
What does checkdb recommend for a repair level?None. Those errors are not repairable.
Then hopefully there are good backups.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
February 25, 2010 at 7:33 am
I can tell you how to fix this, but you are not going to like it.
I am going to guess here that this is a database upgraded from SQL 2000. I am further going to guess that this is the first time that you're running CheckDB since the upgrade.
Am I correct with both of those guesses?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 25, 2010 at 7:35 am
Jack Corbett (2/25/2010)
GilaMonster (2/25/2010)
Jack Corbett (2/25/2010)
What does checkdb recommend for a repair level?None. Those errors are not repairable.
Then hopefully there are good backups.
I doubt there will be. This looks like a classic 'I'm going to update the system tables, to hell with the consequences' problem on SQL 2000 prior to the 2005 upgrade.
There's ways to fix but they're either hellishly complex or lots and lots of work.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 25, 2010 at 7:41 am
GilaMonster (2/25/2010)
Jack Corbett (2/25/2010)
GilaMonster (2/25/2010)
Jack Corbett (2/25/2010)
What does checkdb recommend for a repair level?None. Those errors are not repairable.
Then hopefully there are good backups.
I doubt there will be. This looks like a classic 'I'm going to update the system tables, to hell with the consequences' problem on SQL 2000 prior to the 2005 upgrade.
There's ways to fix but they're either hellishly complex or lots and lots of work.
Yeah, I actually found a solution on another forum site that suggested making changes to the system tables. No way was I going to suggest that since I'd never done it and, in my opinion, it has to be a last resort and recommended/explained by someone with more knowledge than myself. Like you or Paul.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
February 25, 2010 at 7:44 am
Jack Corbett (2/25/2010)
I actually found a solution on another forum site that suggested making changes to the system tables. No way was I going to suggest that since I'd never done it and, in my opinion, it has to be a last resort and recommended/explained by someone with more knowledge than myself. Like you or Paul.
That is actually the best fix, on SQL 2000. On 2005, I could probably hack the system tables successfully to fix something like this, I'd rather not. I know Paul's said the same thing.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply