// SQL Server error reference

SQL Server error 825: Read retry succeeded after failing

A read failed and then succeeded on retry. Nothing failed for the user yet, but it's an early warning of failing storage.

Error number
825
Severity
10
Category
Corruption and I/O
Error message
A read of the file '%ls' at offset %#016I64x succeeded after failing %d time(s) with error: %ls. Additional messages in the SQL Server error log and operating system error log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

What it means

When a read fails with an 823 or 824 condition, SQL Server retries it up to four times. If a retry succeeds, the query continues and SQL Server logs 825 at severity 10. Users don't see an error, which makes 825 easy to miss, but it means the storage is returning errors and real 823/824 failures may follow.

Common causes

  • Disks or storage paths that are beginning to fail.
  • Intermittent driver, firmware or network storage problems.

How to fix it

  1. Set up an alert for error 825 so it isn't missed.

    EXEC msdb.dbo.sp_add_alert @name = N'Error 825 - read retry', @message_id = 825, @severity = 0, @include_event_description_in = 1;
  2. Run DBCC CHECKDB and investigate the storage before it gets worse.

    DBCC CHECKDB (N'SalesDb') WITH NO_INFOMSGS;
  3. Make sure recent backups exist and are restorable.

Related errors

More corruption and i/o errors

The code and message text are from the Microsoft Database Engine events and errors reference. Browse the full SQL Server error list or search every database error.

// fewer errors, faster fixes

Work on SQL Server in SQLly

A native SQL client for macOS, Windows and Linux with schema-aware IntelliSense, guardrails for risky statements and clear error messages, for SQL Server and the other databases you use.