Link to home
Start Free TrialLog in
Avatar of SD_Bolts
SD_BoltsFlag for United States of America

asked on

SQL 2000 msdb (Suspect)

I have one Server (MS Windows Server 2003, Standard Edition) with SQL 2000.  The other day the servers drive where SQL is hosted ran out of disk space.  I was able to make some room for now to get things up and running again.  I was updating information to another database when I noticed that the msdb was marked (Suspect).  I have tried to both back it up from a back up tape and to restore the database through SQL and a back up software.

I was reading another post on the subject and tried to run the Quarry Analyzer but the msdb database did not show up in the list.  I know there are other post on the subject but my experience with SQL is very limited.  I suspect that this is causing one of my other databases in the same SQL to run at limited capacity.
Avatar of lnkevin
lnkevin
Flag of United States of America image

When you have Suspect is when you are running out of the space again. You told us that you cleared out some space, but it suspects that the current available space does not cover the restoration and the restore is unable to complete. Login SQL command and do the following thing:

- Execute sp_resetstatus.
- Use ALTER DATABASE to add a data file or log file to the database.
- Stop and restart SQL Server.
- With the extra space provided by the new data file or log file, SQL Server should be able to complete recovery of the database.
- Free disk space and rerun recovery.

K

Avatar of SD_Bolts

ASKER

Are you referencing the Quarry Analyzer, because it will not let me do that, I am a true novice when it comes to SQL.

I am sorry for taking so long to respond, I had to depart the office for an extended period of time.
ASKER CERTIFIED SOLUTION
Avatar of lnkevin
lnkevin
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I was able to restore the file with the assistance of an individual who is more advanced than I in SQL Databases.