November 19, 2010 at 12:09 am
Dear All,
When I ran DBCC CHECKDB('abc') with no_infomsgs I got the below error.
"Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=973246522,referenced_minor_id=1) of row
(class=0,object_id=1531868524,column_id=0,referenced_major_id=973246522,referenced_minor_id=1) in sys.sql_dependencies does not have a matching row (object_id=973246522,column_id=1) in sys.columns.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=973246522,referenced_minor_id=1) of row
(class=0,object_id=863342140,column_id=0,referenced_major_id=973246522,referenced_minor_id=1) in sys.sql_dependencies does not have a matching row (object_id=973246522,column_id=1) in sys.columns.
CHECKDB found 0 allocation errors and 2 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 2 consistency errors in database 'abc'.
I got the below solution in Google.
1.First, edit the system tables in SQL 2005, which is a complex and very risky process, as the system tables are not documented and are much more complex than they were on previous versions.
2.The other solution is to generate scripts of all the objects in the database and export all of the data. Create a new database, recreate the objects and reload the data.
The second option is usually the recommended one.
So, Iam planning to go for second option.
Can some one please advise how to export all of the data from old database to new database in SQLServer 2005.
Your quick response is much appreciated.
Thanks and Regards,
Ravichandra.
November 19, 2010 at 12:46 am
You don't need to export and recreate the database, there's an easy fix for this corruption that works in most cases
See http://sqlinthewild.co.za/index.php/2009/08/26/corruption-in-sysdependencies/
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
November 22, 2010 at 1:54 am
Thanks Gail Shaw.
It was worked and also I have ensured by running DBCC CHECDB once again.
Now fine.
Regards,
Ravichandra.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply