Suspect SQL Server 2000 Database

By:   |   Comments (3)   |   Related: > SQL Server Configurations


I have a SQL Server 2000 database that has the wrong database status.  For some reason it is in the 'Suspect\Offline' mode. I just need to correct the problem quickly and get my database back online.  How can I do so? Once the status is correct, do I need to take any further steps?


To cut to the chase, the script below can be used to correct the SQL Server 2000 database status, but in reality this is only a third of the equation.  We also need to correct any sort of corruption and understand why this occurred in the first place.

Database Status Correction Script

The script below will change the database to be in simple recovery mode, which may or may not be the needed configuration for your database.  As such, it is necessary to review your database configurations once this script has been executed.  In addition, it is necessary to change the 'YourDatabaseName' to your database name in single quotes.

USE Master

-- Determine the original database status
SELECT [Name], DBID, Status
FROM master.dbo.sysdatabases

-- Enable system changes
sp_configure 'allow updates',1

-- Update the database status
UPDATE master.dbo.sysdatabases
SET Status = 24
WHERE [Name] = 'YourDatabaseName'

-- Disable system changes
sp_configure 'allow updates',0

-- Determine the final database status
SELECT [Name], DBID, Status
FROM master.dbo.sysdatabases

Check for Corruption

The next step in this process is very key.  It is necessary to determine if the database has any corruption and ensure that the database will be able to support the users.  If the database has corruption, you may be exposing yourself to more issues by just changing the database status without correcting the underlying issue.  To identify the underlying issue, execute the following commands:

  • DBCC CHECKDB - Validate the overall database integrity
  • DBCC CHECKCATALOG - Validate the system catalog integrity
  • DBCC CHECKTABLE - Validate the integrity for a single table

To resolve the issue, you may need to do one or more of the following:

  • Drop and Recreate Index(es)
  • Move the recoverable data from an existing table to a new table
  • Update statistics
  • sp_recompile

To ensure the issue is corrected, it is a good idea to re-run the identification commands listed above and validate that they do not have any issues.

To address these items, check out the following

Determine the Root Cause

In the long term, it is imperative to understand what caused the suspect/offline database.  At a minimum the following questions should be addressed:

  • What has recently changed in your environment?
  • Review your SQL Server logs to see if you can determine when the error occurred.
  • Talk to your team members to ask them what changes have been made.
  • Review your change management and auditing processes to see what has changed in SQL Server or at a systems level.
  • See if the issue has occurred on any other databases in your environment.
Next Steps

sql server categories

sql server webinars

subscribe to mssqltips

sql server tutorials

sql server white papers

next tip

About the author
MSSQLTips author Jeremy Kadlec Jeremy Kadlec is a Co-Founder, Editor and Author at with more than 300 contributions. He is also the CTO @ Edgewood Solutions and a six-time SQL Server MVP. Jeremy brings 20+ years of SQL Server DBA and Developer experience to the community after earning a bachelor's degree from SSU and master's from UMBC.

This author pledges the content of this article is based on professional experience and not AI generated.

View all my tips

Comments For This Article

Wednesday, May 21, 2014 - 1:51:24 AM - JSanz Back To Top (30864)

great tips - thank you.

Monday, October 8, 2012 - 5:24:57 AM - Kale Balkrishna Back To Top (19816)


Thankyou very much, I am able to recover suspect database after using the commands above.

Monday, November 10, 2008 - 2:22:03 PM - Dominique Back To Top (2186)


These articles are great as they solved my issues..

But as a local administrator I was not able to see any databases in SQL Enterprise Manager having a login failed for any account I was using.

Only a Domain Administrator was able to access it and let me correct the issue... which permissions was missing for me to be able to do the same correction on SQL without being a domain administrator?

I am dbo on several databases and also sysadmin role on them.

Should I be dbo on master? will it be enough?

Thank you,

get free sql tips
agree to terms