Please pardon any ignorance on my part...(brand-spanking-new-DBA)Running CheckDB returns the following error:Check Catalog Msg 3853, State 1: Attribute (object_id=1357963914) of row (object_id=1357963914,column_id=1) in sys.columns does not have a matching row (object_id=1357963914) in sys.objects. [SQLSTATE 42000] (Error 8992) CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object. [SQLSTATE 01000] (Error 8954) CHECKDB found 0 allocation errors and 1 consistency errors in database 'amtslab'. [SQLSTATE 01000] (Error 8989). The step failed.I found this article: http://www.sqlservercentral.com/articles/Corruption/69382/[quote]The method preferred by most of the SQL corruption gurus is to create another database, and copy the contents of the corrupted database into the new database. Depending on the size of your database, this could take quite some time.[/quote]Could you tell me...what is involved with "copying the contents of the corrupted db to the new db?" Is the article referring to manually transferring all the data and objects? If so, is there any tool that could assist?Also, this error apparently has been happening for quite some time (the server was upgraded some time ago and we just began recently to run CheckDB) and all copies of this db on our other intances and all backups copies appear to have this issue. Is it something that MUST be repaired? If it is something we can get by with, should and could we repress the errors so CheckDB could continue?Also, when I query sys.columns and sys.objects for object_id 1357963914 I do not get any records returned.Any information you have to offer would be greatly appreciated. TIA!
↧