Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

Help! My Database is Marked Suspect.

By Brian Knight, (first published: 2004/03/31)

A database can be marked for many reasons. Generally it falls into the following conditions :
  • A database or log file is missing.
  • In SQL 6.5, a device may not be present or in 7.0/2000 a file may not exist.
  • SQL Server may not have been able to restore the database in ample time.
  • The database could be corrupt.
  • The database is being help by the operating system. This could be a 3rd party backup software or defrag software. I've had even a virus scanning software cause this once.
  • SQL Server does not have enough space to recover the database on startup.

To fix this problem, perform the following functions:

  1. Review the SQL Server and NT error logs to see if you can find where the problem occured.
  2. Start SQL Server in single user mode.
    • Go to your control panel and services.
    • Stop SQL Server
    • Add the -m switch in the parameters pane below.
    • Start SQL Server
  3. Run sp_resetstatus with the @dbname parameter. (ie : sp_resetstatus @dbname = "pubs")
  4. Perform detailed DBCC checks (CHECKDB, CHECKALLOC, etc)
  5. Run a few random queries to see if you experience any problems.
  6. If no problems occur, stop and start SQL Server and open the database to production.

    As an absolute last resort, you can place your database in emergency mode. By placing it in this mode, you will be allowed to copy data out of the database, even if the data is corrupt. To place your database in emergency mode, use the following command:

    SP_CONFIGURE 'allow updates', 1
    RECONFIGURE WITH OVERRIDE
    GO
    UPDATE master..sysdatabases set status = -32768 WHERE name = 'pubs'
    GO
    SP_CONFIGURE 'allow updates', 0
    RECONFIGURE WITH OVERRIDE

    You can then BCP data out and place it into a different database.

Total article views: 57749 | Views in the last 30 days: 37
 
Related Articles
FORUM

dbcc allow data lose problem with increasing log

dbcc allow data lose problem with increasing log

FORUM

database problem

database problem

FORUM

Maximum size of a database that SQL Server 2005 clustered allows

Maximum size of a database that SQL Server 2005 clustered allows

FORUM

Problem in database restore

Problem in database restore

FORUM

Problems in Database mail in SQL server 2005

Problems in Database mail in SQL server 2005

Tags
 
Contribute

Join the most active online SQL Server Community

SQL knowledge, delivered daily, free:

Email address:  

You make SSC a better place

As a member of SQLServerCentral, you get free access to loads of fresh content: thousands of articles and SQL scripts, a library of free eBooks, a weekly database news roundup, a great Q & A platform… And it’s our huge, buzzing community of SQL Server Professionals that makes it such a success.

Join us!

Steve Jones
Editor, SQLServerCentral.com

Already a member? Jump in:

Email address:   Password:   Remember me: Forgotten your password?
Steve Jones