%1 (%2) %3Database %4: Page %5 failed verification due to a timestamp mismatch. The expected timestamp was %6 but the actual timestamp on the page was %7. Recovery/restore will fail with error %8. If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware "losing" one or more flushes on this page sometime in the past. Please contact your hardware vendor for further assistance diagnosing the problem. For more information, click http://www.microsoft.com/contentredirect.asp.
Database %4 requires logfiles %5-%6 in order to recover successfully. Recovery could only locate logfiles starting at %7. ...
Database %4 requires logfiles %5-%6 in order to recover successfully. Recovery could only locate logfiles up to %7. For more ...
Database %4 was partially detached. Error %5 encountered updating database headers. For more information, click http://w ...
Database %4: Page %5 failed verification due to a flush-order dependency mismatch. This page should have flushed before page ...
Database %4: Page %5 failed verification due to a timestamp mismatch. The expected timestamp was %6 but the actual timestamp ...
Database %6: Index %4 of table %5 is corrupted (%7). For more information, click http://www.microsoft.com/contentredirect.asp. ...
Database '%1': A message was successfully delivered, but an error (%2) was encountered attempting to add an entry for it ...
Database '%1': A message with an expiration time was successfully delivered, but an error (%2) was encountered attempting ...
Database '%4': Available B-Tree IDs (ObjectIDs) have almost been completely consumed. Freed/unused B-Tree IDs may be reclaimed ...