![]() So what do you do? The first instinct is to think, 'Restore! Restore! Restore!' But in this scenario, this will involve the following steps as a minimum: As this sample error reports, there's a problem in the 'corruption_secondary.mdf' file (my second data file in this test database) at page 3:0, offset 000.000 (right at the beginning). It is clear that the SQL Server database integrity has been compromised. This error can be caused by many factors for more information, see SQL Server Complete a full database consistency check (DBCC CHECKDB). ![]() This is a severe error condition that threatens database integrity and must beĬorrected immediately. Messages in the SQL Server error log or system event log may provide more detail. ![]() It occurred during a read of page (3:0) in database ID 10 at SQL Server detected a logical consistency-based I/O error: unable to decrypt pageĭue to missing DEK.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |