August 9, 2012 at 12:25 am
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=292300201) of row (object_id=292300201,column_id=1) in sys.columns does not have a matching row (object_id=292300201) in sys.objects.
object_id exist in sys.columns and not exist in sys.objects
and sys.tables
I try CHECKDB
August 9, 2012 at 12:34 am
Pls provide the query which gave this error
Thanks
August 9, 2012 at 12:44 am
DBCC CHECKDB give this error
August 9, 2012 at 2:47 am
Looks like logical corruption.
I would restore from backup if possible.
There's another method, but I won't disclose it unless you have no backups.
-- Gianluca Sartori
August 9, 2012 at 5:40 am
This is the solution but i am going to try it
August 9, 2012 at 6:33 am
This is the solution I had in mind.
If you feel confident, try it. If it was my database, I would restore from backup.
-- Gianluca Sartori
August 9, 2012 at 6:49 am
Restore database dosen't solve this problems
because backup of database involve system tables of
database This the main problem query
SELECT * FROM SYS.columns CLM WHERE CLM.OBJECT_ID
NOT IN (SELECT OBJ.object_id FROM SYS.objects OBJ )
First i will try it in my test envoirment we talk about 650 gb
and 2500 request/per second
August 9, 2012 at 6:52 am
ESAT ERKEC (8/9/2012)
Restore database dosen't solve this problemsbecause backup of database involve system tables of
database
I suggest running CHECKDB more often than you're doing.
Taking a backup of a corrupt database is totally pointless, as you can see.
-- Gianluca Sartori
August 9, 2012 at 6:55 am
This is correct my friend
August 9, 2012 at 6:58 am
ESAT ERKEC (8/9/2012)
Why wouldn't a restore of the database solve the problem? As long as the corruption did not exist at the time of the backup, it should correct the problem.
August 9, 2012 at 7:00 am
How can i merge production db and backup in sys.objects ?
August 9, 2012 at 7:02 am
ESAT ERKEC (8/9/2012)
How can i merge production db and backup in sys.objects ?
Sorry, can you rephrase? I don't think I understand what you mean.
-- Gianluca Sartori
August 10, 2012 at 5:54 am
Lynn Pettis (8/9/2012)
ESAT ERKEC (8/9/2012)
This is the solution but i am going to try itWhy wouldn't a restore of the database solve the problem? As long as the corruption did not exist at the time of the backup, it should correct the problem.
Big if...
That corruption is usually from prior to SQL 2005 upgrade, from edits made to the system tables in SQL 2000.
If the backup is clean, it can be restored, personally I'd bet it isn't clean.
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
August 10, 2012 at 5:56 am
ESAT ERKEC (8/9/2012)
How can i merge production db and backup in sys.objects ?
You can't merge a database and a backup
If the backup is clean, restore it as another name and then sync the data.
If the backup is not clean, script all objects, export all data, recreate the DB.
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
August 10, 2012 at 6:42 am
All backup have the same problem.
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply