![]() I have few queries it is not related with corrupt demo databases but some points I have Googled for suspect database, it is in that regards.Īs I know the database should be restored from backup and logs reapplied. Is there a problem having such corrupted page into the database ? How to drop it ? So I wonder what exactly does ALLOW_REPAIR_ALLOW_DATA_LOSS, and how to control his action ? And if I try a DBCC PAGE on the corrupted page, I still have the error :Ī DBCC PAGE error has occurred: Invalid page type – dump style 3 not possible. Repair: The page (1:6196) has been deallocated from object ID 1333579789, index ID 0, partition ID 72057594041335808, alloc unit ID 72057594057654272 (type In-row data).Ī second checkDB give me no error any more, the database is now clean.īut it seems that actually the corrupted page has not been dropped. Now I’ve the records concerned by the corruption, I’ve launched a CHECKDB REPAIR_ALLOW_DATA_LOSS on the corrupted database as I was thinking that the corrupted page would be dropped. I’ve found the primary key of the records into the page, then identified the missing rows by a SELECT of the primary key values into the restored and clean database. I’ve restored the last backup (simple mode recovery) and found out the data that were into the corrupted page by using DBCC pages (actually there was only four rows into the page : m_SlotCnt = 4). Fortunately only one data page was corrupted: I’ve encoutered a corruption on a production database. The scripts zip contains the following directories: Note that I have not created DemoFatalCorruption databases yet for 2012.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |