Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).


Product Name

SQL Server

Event ID


Event Source




Symbolic Name


Message Text

During redoing of a logged operation in database '%.*ls', an error occurred at log record ID %S_LSN. Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.


This is a roll-up error for redo recovery. This error has placed the database into the SUSPECT state. The primary filegroup, and possibly other filegroups, are suspect and may be damaged. The database cannot be recovered during startup of SQL Server and is therefore unavailable. User action is required to resolve the problem.

Note that if this error occurs for tempdb, the SQL Server instance shuts down.

User Action

This error can be caused by a transient condition that existed on the system during a given attempt to start up the server instance or to recover a database. This error can also be caused by a permanent failure that occurs every time that you attempt to start the database. For information about the cause, examine the Windows Event Log for a previous error that indicates the specific failure.

Note that when this error condition is encountered, SQL Server typically generates three files in the SQL Server LOG folder. The SQLDumpnnnn.txt file contains advanced diagnostic information relating to the failures, including the details about the transaction and the page that encountered the problem. This information is typically used by the Product Support team to analyze the reason for the failure.

For information about the cause of this occurrence of error 3313, examine the Windows Event Log for a previous error that indicates the specific failure. The appropriate user action depends on whether the information in the Windows Event Log indicates that the SQL Server error was caused by a transient condition or a permanent failure. For information about the user actions for troubleshooting error 3313, see SQL Server Books Online.

See Also




sys.databases (Transact-SQL)


Complete Database Restores (Simple Recovery Model)