Database %1: Page %2 failed verification due to a timestamp mismatch. The expected timestamp was %3, but the actual timestamp on the page was %4. Recovery/restore will fail with error %5. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware previously losing one or more flushes on this page. Please contact your hardware vendor for further assistance with diagnosing the problem.
Database %1 requires log files %2-%3 in order to recover successfully. Recovery could only locate log files starting at %4. ...
Database %1 requires log files %2-%3 in order to recover successfully. Recovery could only locate log files starting at %4. ...
Database %1: Page %2 failed verification due to a flush-order dependency mismatch. This page should have flushed before page ...
Database %1: Page %2 failed verification due to a flush-order dependency mismatch. This page should have flushed before page ...
Database %1: Page %2 failed verification due to a timestamp mismatch. The expected timestamp was %3, but the actual timestamp ...
Database %1: Page %2 failed verification due to a timestamp mismatch. The expected timestamp was %3, but the actual timestamp ...
Database %4 cannot be incrementally backed-up. You must first perform a full backup before performing an incremental backup. ...
Database %4 cannot be incrementally backed-up. You must first perform a full backup before performing an incremental backup. ...
Database %4 has lost %5 committed log files (%6-%7). However, lost log resilience has allowed ESE to recover this database ...