Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Check Catalog Msg 3853, State 1: Expand / Collapse
Author
Message
Posted Friday, August 10, 2012 7:25 PM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 1:13 PM
Points: 774, Visits: 1,734
Hi All,

Just wanted to know what does this error mean? I do see a lot issues with this meta data corruption during upgrade of sql 2000 to sql 2008.

What does happen during the upgrade ?
What are the possible sceanori's we land up in such scenarios? As far as i know i if someone changes the system tables, this might cause this errrors. Just wanted to understand why upgrade to higher version causes this meta data corruption. I beilve we should run the checkdb on sql 2000 databases even before going for upgrade !!!

Check Catalog Msg 3853, State 1: Attribute (object_id=1379457380) of row (object_id=1379457380,column_id=1) in sys.columns does not have a matching row (object_id=1379457380) in sys.objects

Thanks in Advance
Post #1343729
Posted Saturday, August 11, 2012 3:15 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 3:46 PM
Points: 42,462, Visits: 35,525
Root cause is that back on SQL 2000 someone messed with the system tables (via allow updates being set to 1). On SQL 2000, CheckDB doesn't run checkcatalog so the error goes unnoticed until the upgrade, when things break badly sometimes. It's not that the upgrade is causing the error, it's just finding an error that existed for some time already

This is easy to fix if you find it before the upgrade, it's extremely difficult to fix afterwards. Best thing is to run CheckCatalog on the SQL 2000 DB before upgrading, then fix any errors that appear.




Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1343767
Posted Saturday, August 11, 2012 11:08 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 1:13 PM
Points: 774, Visits: 1,734
Makes sense. Thanks Gail for the clarifications.
Post #1343809
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse