%1 (%2) %3Database %4: Page %5 failed verification due to a flush-order dependency mismatch. This page should have flushed before page %6, but the latter page has instead flushed first. Recovery/restore will fail with error %7. 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 one or both of these pages sometime in the past. Please contact your hardware vendor for further assistance diagnosing the problem.
Data width of the physical memory, in bits. A data width of 0 and a total width of 8 would indicate that the memory is solely ...
Database %4 cannot be incrementally backed-up. You must first perform a full backup before performing an incremental backup. ...
Database %4 requires logfile %5 created at %6 in order to recover successfully. Recovery found the logfile created at %7. ...
Database %4 requires logfiles %5-%6 in order to recover successfully. Recovery could only locate logfiles starting at %7. ...
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 '%4': Available B-Tree IDs (ObjectIDs) have almost been completely consumed. Freed/unused B-Tree IDs may be reclaimed ...
Database '%4': Background clean-up skipped pages. The database may benefit from widening the online maintenance window during ...
Database '%4': Out of B-Tree IDs (ObjectIDs). Freed/unused B-Tree IDs may be reclaimed by performing an offline defragmentation ...