| title | MSSQLSERVER_926 | |
|---|---|---|
| description | MSSQLSERVER_926 | |
| author | MashaMSFT | |
| ms.author | mathoma | |
| ms.date | 04/04/2017 | |
| ms.service | sql | |
| ms.subservice | supportability | |
| ms.topic | reference | |
| helpviewer_keywords |
|
[!INCLUDE SQL Server]
| Attribute | Value |
|---|---|
| Product Name | SQL Server |
| Event ID | 926 |
| Event Source | MSSQLSERVER |
| Component | SQLEngine |
| Symbolic Name | DB_SUSPECT |
| Message Text | Database '%.*ls' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information. |
The database is marked as suspect because it failed the recovery process that brings a database to a consistent transactional state. This can occur during the following operations:
-
Starting up an instance of [!INCLUDEssNoVersion].
-
Attaching a database.
-
Using the RESTORE database or RESTORE LOG procedures.
Inspect the [!INCLUDEssNoVersion] error log and determine the cause of the error. If [!INCLUDEssNoVersion] has been restarted since the failed recovery, look at previous [!INCLUDEssNoVersion] error logs to see the reason why recovery failed.
If the recovery failed because of a persistent I/O error, a torn page, or other possible hardware problem, resolve the underlying hardware problem and restore the database by using a backup. If no backups are available, consider the repair options of DBCC CHECKDB.
If you are unable to resolve this problem, contact your primary support provider. Have the [!INCLUDEssNoVersion] error log available for review.
Back Up and Restore of SQL Server Databases
RESTORE (Transact-SQL)
sys.sysdatabases (Transact-SQL)
Database Detach and Attach (SQL Server)