InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 22 May 2013 23:18:28 GMT20http://www.sqlservercentral.com/Forums/Topic1343729-2893-1.aspxMakes sense. Thanks Gail for the clarifications. :-)Sat, 11 Aug 2012 11:08:35 GMTOracle_91http://www.sqlservercentral.com/Forums/Topic1343729-2893-1.aspxRoot 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 alreadyThis 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.Sat, 11 Aug 2012 03:15:46 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1343729-2893-1.aspxHi 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.objectsThanks in AdvanceFri, 10 Aug 2012 19:25:26 GMTOracle_91