MSDB in suspect mode.

Hi,
I have mssql 2005 installed and i see that MSDB database is marked as suspect. I almost tried all the steps which are submitted in the forums.
1) I shut down the server, navigating to the directory 'd:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn' and doing the following: start sqlservr.exe -c -T3608
2) renamed the damaged msdb files (msdbdata.mdf and msdblog.ldf in the 'd:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data' directory)
3) Run the instmsdb.sql script in the 'd:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install' directory
--x---
When I executed third step it returned me below error:
Msg 926, Level 14, State 1, Line 63
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
Please advice me.

Hi,
As the DB was in the suspect mode it didn't gave me scope to detach the DB. Now the DB is out of suspect mode after succesfully completing the 3rd step of your blog.
However the another issue I found while going through the script (in your blog), instmsdb.sql while going to create msdb database uses the same path of master db. while actual path in the sysdatabase for msdb database is different than master db.
Also 3rd steps is completed succesfully but it doesn't create database anywhere due to this msdb is out of suspect mode but as it doesn't see physical file as per the path specified in sysdatabase it doesn't work and gives below error while accessing properties of any database:
Database 'msdb' cannot be opened due to inaccessible files or insufficient memory or disk space

Similar Messages

  • Database in Suspect Mode in SQL Server 2000 Log Shipping Environment

    Hi All
    We have movement of SQL Server 2000 at physical level. We have disable jobs and stop Agent and SQL Server services.
    After moved the server we have started the server and then start SQL Server 2000 services.
    All of databases in SUSPECT mode. Files are in correct folders as were before shutdown the server
    What shall I do e.g. why databases come up in SUSPECT mode? what to check and how to get database live?
    Pls help it is critical...
    Thanks in Advance

    All of databases in SUSPECT mode. Files are in correct folders as were before shutdown the server
    What shall I do e.g. why databases come up in SUSPECT mode? what to check and how to get database live?
    Pls help it is critical...
    Thanks in Advance
    Hello,
    Did you made sure no transactions like restore logs  were running when you stopped SQL server service or agent .I have seen in SQL 2000 an abrupt stop of SQL Server agent when its doing a process can sometimes force database in suspect mode.
    I would like you to get your disk analyzed by vendor ASAP for any fault in disk at first go it seems to me an underlying hardware issue.
    Please can you check errorlog and event viewer to find out any possible cause for database going into suspect mode
    I always suggest to use Backup and restore method of recovery to get out from suspect database problem.If you dont have then you can move with DBCC Checkdb and various repair options but be sure
    DATA LOSS might be possible when you use repair allow data loss and repair_rebuild removes constraints.
    hope this helps
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Database in suspect mode

    i was going through this article about recovering a database in suspect mode :
    http://www.mytechmantra.com/LearnSQLServer/Repair_Suspect_Database_P2.html
    in the article the error seems to indicate corruption in the log :
    Error: 9003, Severity: 20, State: 9. The log scan number (189624:16:2) passed to log scan in database
    'BPO' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf
    if the corruption is in the log, then is not the logical solution to bypass the recovery process and then truncate the log with no_log option and then bring the database online?
    and dbcc checkdb (<db>,repair_allow_data_loss) repairs the data pages or the log pages?
    and any other options/ways/articles about bringing a suspect database online?
    appreciate the insights.

    datafile corruption : put db in emergency mode / put db in single user mode / dbcc checkdb with REPAIR_ALLOW_DATA_LOSS/ dbcc checkdb on database
    again/put db back in multi user mode.
    There is no need to do this. This is totally not required.
    You can
    Switching the database to the Simple recovery model
    Performing a checkpoint (which should clear the active log as long as nothing else requires the log to be kept active)
    Switching back to the Full recovery model
    Reestablishing the log backup chain by performing a full or differential backup
    Or you can rebuild log as already pointed in my reply.
    Or you can restore from known valid backup.
    There is no need to move data as well because actually its not related to data.
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Recover SQL Server database from SUSPECT mode

    Hi Expert DBAs,
    As I know the database should be restored from backup and logs reapplied. That’s the first and generally recommended approach any time a DB is suspect, whether it’s from log or data file corruption.
    But if I have no backups then we follow below steps ( after Googling I found these steps on most of the websites ):
    1.EXEC sp_resetstatus ‘yourDBname’;
    2.ALTER DATABASE yourDBname SET EMERGENCY
    3.DBCC checkdb(’yourDBname’)
    4.ALTER DATABASE yourDBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE
    5.DBCC CheckDB (’yourDBname’, REPAIR_ALLOW_DATA_LOSS)
    6.ALTER DATABASE yourDBname SET MULTI_USER
    Now my question is, 
    1. If after executing DBCC CHECKDB at 3rd step, it shows inconsistency.Then I will execute SET SINGLE USER WITH ROLLBACK & if after executing DBCC CHECKDB at 3rd step, no errors found. Then what will be the steps?
    2. When we execute DBCC CHECKDB (' DBNAME ', REPAIR_ALLOW_DATA_LOSS) how can we recover lost data during process.As far as I know some data will loss and if it will happen then business will get suffered.
    3. Why run DBCC CHECKDB() WITH REPAIR_ALLOW_DATA_LOSS if there are no consistency errors in the database?
    I am stucked in these questions....
    Regards,
    Yashwant Vishwakarma | SQLOcean.com
    Yashwant Vishwakarma | www.sqlocean.com

    There is no easy or same steps, it all depends on what error and what caused suspect. 
    Example is below:
    http://www.sql-server-performance.com/2015/recovery-sql-server-suspect-mode/
    2) Straight answer would be no you cant recover if no backup. Again it all depends what error checkdb returns and some things can be tried as explained earlier but no guarantee.
    The REPAIR_ALLOW_DATA_LOSS option is not the best option for bringing a database to a physically consistent state. If successful, the REPAIR_ALLOW_DATA_LOSS option may result in some data loss. In fact, it may result in more data lost than if a user were to
    restore the database from the last known good backup. Microsoft always recommends a user restore from the last known good backup as the primary method to recover from errors reported by DBCC CHECKDB. The REPAIR_ALLOW_DATA_LOSS option is not an alternative
    for restoring from a known good backup. It is an emergency “last resort” option recommended for use only if restoring from a backup is not possible.
    Certain errors, that can only be repaired using the REPAIR_ALLOW_DATA_LOSS option, may involve deallocating a row, page, or series of pages to clear the errors. Any deallocated data is no longer accessible or recoverable for the user, and the exact contents
    of the deallocated data cannot be determined. Therefore, referential integrity may not be accurate after any rows or pages are deallocated because foreign key constraints are not checked or maintained as part of this repair operation. The user must inspect
    the referential integrity of their database (using DBCC CHECKCONSTRAINTS) after using the REPAIR_ALLOW_DATA_LOSS option.
    https://msdn.microsoft.com/en-us/library/ms176064.aspx

  • Database mssql server 2008 is in suspect mode?

    Database sql server 2008 is in suspect mode and I am not able to bring the database online and i have no backup to restore.
    To resolve this issue run the commands listed below,
    EXEC sp_resetstatus ‘DATABASE_NAME’;
    ALTER DATABASE DATABASE_NAME SET EMERGENCY
    DBCC checkdb(‘DATABASE_NAME’)
    ALTER DATABASE DATABASE_NAME SET SINGLE_USER WITH ROLLBACK IMMEDIATE
    DBCC CheckDB (‘DATABASE_NAME’, REPAIR_ALLOW_DATA_LOSS)
    ALTER DATABASE DATABASE_NAME SET MULTI_USER
    But there will be data loss if i execute the above queries.
    Is there any alternate solution for this?
    Can anyone help me please.

    You can use DBCC CheckDB (‘DATABASE_NAME’, REPAIR_REBUILD) instead of REPAIR_ALLOW_DATA_LOSS, which will not cause data loss.
    You can get more info at Recover a Corrupt SQL Server MDF Database
    For any cases, the best practise is to backup of your corrupt MDF database first.

  • Database in suspect mode...why does it happen?

    I am using SQL 2012 SE with A-P clustering. We had an automatic failover around 3:00AM and the replication publisher database went into suspect mode. I gave it some time to see if it would come back to normal mode all by itself and when it did not I took
    the db to emergency mode and then single user mode and did dbcc check and then when there were no errors I tried to bring it to multi user mode and it would still remain in emergency mode.
    I tried to do take it offline and bring it online.But it wont go offline as it says database is in replication and cannot be taken offline. So I had to broke replication and take the database offline and brought it back online and then restarted the replication
    from scratch.
    I came to know that the LUN went offline and then came back online and that triggered the failover. 
    But, why did the publisher database go to suspect mode? I told my IT manager that the underlying disk that went offline was hosting the publisher database and since the disk went down and came back it took the database to suspect mode but he would believe it.
    Is there a way that we can tell for sure that a specific issue caused the database go to suspect mode? Like any log/eventvwr? I had transaction log backups running like once every 10 mins for publisher database...could that be a reason?
    Also are there any specific causes that will take a database into suspect mode?
    Thanks a ton

    From my experience  most of the problems because of physical disk failure ... look also into Event Viewer.
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • Availability Group Database( secondary) went to Suspect mode. What is the solution?

    Hi Folks,
    database went suspect mode in secondary server. ( sql 2012 SP1)
    1. How to bring online,Is it possible withuot breaking primary.
    2. can we access only primary.
    3. What are the modes ( not_synchronzing, suspnded etc.)
    Could you please explain , how to bring databace into synchronzing mode.
    Many Thanks.

    Any info in the ERROL.LOG,Event Viewer??? Generally, databases go into suspect mode because disk failure ,io..
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • What is SUSPECT Mode database?

    Hi All,
    What is suspect mode in sql server and how it happens and how to recover from the suspect database ?\
    Please post the article.
    Thanks&Regards Siva G

    SQL server marks database as suspect due to many reasons; some of them are given below:
    Hardware failure
    Improper shutdown of the database server
    Corruption of the database files
    Unavailable device files
    Unavailable database files
    Database resource used by operating system
    SQL Server incorrectly asserts free data page space when a row is inserted 
    For details click here
    http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
    http://www.stellarsqldatabaserecovery.com/repair-suspect-sql-server.php
    http://sql-server-recovery.blogspot.in/2010/10/repair-restore-sql-server-database-from.html
    http://www.slideshare.net/warnor/how-to-restore-sql-server-database-from-suspect-mode
    Read my blog (Blog)
    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

  • Database in Suspended Mode

    Hi,
    I faced this problem suddenly when i was trying some indexes on a local dummy table(using 'sa' user id) on DB COSMOS. After working around indexes i saved the file and closed Query Analyzer. On relogging again with 'sa' user Id i faced the following problem "A connection was successfully established but then an error occured during the login process.(provider : Shared Memory Provider, error:0 - No process is on the other end of the pipe.) "
    Then i logged in with Windows Authentication account. however i couldnt access DB COSMOS as it was put in Suspended Mode. On checking the event viewer i found below error
    "SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0xb42e9a1f; actual: 0xb45a9f73). It occurred during a read of page (2:0) in database ID 7 at offset 0000000000000000 in file 'E:\COSMIC\COSMOS_log.ldf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online."
    Well how the above error can be repaired. There are no backups of this db. I cannot run DBCC CHECKDB command for COSMOS as the same has been suspended.
    Please give me the solution to above problem.
    Thanks

    Hi ,
    Thanks for the info. Lekss thanks for that article..it was quite useful.
    Please check the below error that i found in error log.
    2009-12-29 21:09:45.81 spid20s     Error: 824, Severity: 24, State: 2.
    2009-12-29 21:09:45.81 spid20s     SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0xb42e9a1f; actual: 0xb45a9f73). It occurred during a read of page (2:0) in database ID 7 at offset 0000000000000000 in file 'E:\COSMIC\COSMOS_log.ldf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    2009-12-29 21:09:45.81 spid20s     Error: 3414, Severity: 21, State: 2.
    2009-12-29 21:09:45.81 spid20s     An error occurred during recovery, preventing the database 'COSMOS' (database ID 7) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
    2009-12-29 21:09:45.85 spid53      EMERGENCY MODE DBCC CHECKDB (COSMOS, repair_allow_data_loss) WITH no_infomsgs executed by HOME\ADMIN terminated abnormally due to error state 5. Elapsed time: 0 hours 0 minutes 1 seconds.
    by putting my DB in emergency mode i could get the tables.Luckily there were only ten tables. however how do i take backup of the entire database in this case. As mentioned above, on executing DBCC CheckDB ('DBname', REPAIR_ALLOW_DATA_LOSS) after setting dB to single User mode, the system still displayed that the dB was in suspect mode and cannot be opened. Also the other system dbs including master is damaged and in Online mode. how do i get damaged free dBs. What should be done in real live situation where data is very important.

  • Database in Emergency Mode

    Hi All.. i have had one database was in suspect mode and i have changed the status to Emergency Mode and  i have run the DBCC checkdb and command didn't gave any error.. after this i have tried to change database to Single_user mode, but command running
    successfully, but database status is still showing as Emergency mode only.. i have tried for multi_user mode too..
    Also, i have tried to run the command to bring online, but command running for long time with Suspended status..
    Could anyone help me on this??

    Hi Balajik,
    "Also, i have tried to run the command to bring online, but command running for long time with Suspended status.."
    In addition to other post, please check the following things.
    1. Run sp_who2 to check that if there is blocked process. If blocked process exists, run “KILL <spid>“ to kill it.
    2. Make sure that there are no connections to the database from other applications. You can run the below scripts to find connections.
    USE master
    SELECT * FROM sys.sysprocesses WHERE dbid = DB_ID('DatabaseName')
    3. You might need to stop and start SQL Server Service using SQL Server Management Studio, then check if you can set the database online.
    Besides, to recover database which is in emergency mode, you can review the following similar thread.
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/4186ba24-5188-4ea9-bb83-f39d44f1897d/database-in-emergency-mode?forum=sqldatabasemirroring
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • Difference between emergency state and single user mode ?

    Hi,
    I want to know the difference between emergency state which we normally use in suspect mode database and single user mode.
    Navakanth

    Emergency/suspect mode is tells you the state of the database and database is not available for user action but where as single user mode tells the user action preference. Database is active and available for the user action.
    You can refer 
    http://msdn.microsoft.com/en-us/library/bb522682.aspx
    EMERGENCY
    The database is marked READ_ONLY, logging is disabled, and access is limited to members of the sysadmin fixed server role. EMERGENCY is primarily used for troubleshooting purposes. For example, a database marked as suspect due to a corrupted log file can be
    set to the EMERGENCY state. This could enable the system administrator read-only access to the database. Only members of the sysadmin fixed server role can set a database to the EMERGENCY state.
    SINGLE_USER
    Specifies that only one user at a time can access the database. If SINGLE_USER is specified and there are other users connected to the database the ALTER DATABASE statement will be blocked until all users disconnect from the specified database. To override
    this behavior, see the WITH <termination> clause.
    The database remains in SINGLE_USER mode even if the user that set the option logs off. At that point, a different user, but only one, can connect to the database.
    Before you set the database to SINGLE_USER, verify the AUTO_UPDATE_STATISTICS_ASYNC option is set to OFF. When set to ON, the background thread used to update statistics takes a connection against the database, and you will be unable to access the database
    in single-user mode. To view the status of this option, query the is_auto_update_stats_async_on column in the sys.databases catalog view.
    If the option is set to ON, perform the following tasks:
    Set AUTO_UPDATE_STATISTICS_ASYNC to OFF.
    Check for active asynchronous statistics jobs by querying the sys.dm_exec_background_job_queue dynamic management view.
    If there are active jobs, either allow the jobs to complete or manually terminate them by using KILL STATS JOB.
    --Prashanth

  • Sybase ASE 15.7.0 in suspect status

    Hi Gurus,
    We have a problem when we try to connect to a SyBase DB (Adaptive Server Enterprise/15.7.0/EBF 20953 SMP ESD#4.2), the database is in suspect mode.
    We ran the following commands after rebooting but the same error appears:
    server>isql -X -Usapsso -S<SID> -w2000 -P<pass>
    1> sp_configure "allow updates", 1
    2> go
    Parameter Name Default Memory Used Config Value Run Value Unit Type
    allow updates to system tables 0 0 1 1 switch dynamic
    (1 row affected)
    Resulting configuration value and memory use have not changed from previous values: new configuration value 1, previous value 1.
    (return status = 0)
    1> quit
    server> isql -X -Usapsa -S<SID> -w2000 -P<pass>
    1> use master
    2> go
    1> begin transaction
    2> go
    1> update sysdatabases
    2> set status = status & ~256
    3> where name="<SID>"
    4> go
    (1 row affected)
    1> quit
    server> isql -X -Usapsso -S<SID> -w2000 -P<pass>
    1> commit transaction
    2> go
    1> sp_configure "allow updates", 0
    2> go
    Parameter Name Default Memory Used Config Value Run Value Unit Type
    allow updates to system tables 0 0 0 0 switch dynamic
    (1 row affected)
    Configuration option changed. ASE need not be rebooted since the option is dynamic.
    Changing the value of 'allow updates to system tables' does not increase the amount of memory Adaptive Server uses.
    (return status = 0)
    1>quit
    server> isql -X -Usapsa -S<SID> -w2000 -P<pass>
    1> checkpoint
    2> go
    1> shutdown
    2> go
    This is the result of executing the following query.
    1> select dbid, name, status, status2, status3, status4 from sysdatabases
    2> go
    dbid name status status2 status3 status4
    1 master 0 -32768 131072 16384
    3 model 0 -32768 131072 16384
    2 tempdb 8716 -32767 131072 540672
    31513 sybsystemdb 0 -32768 131072 16384
    31514 sybsystemprocs 8 -32768 131072 16384
    31515 sybmgmtdb 12 -32768 131072 16384
    4 <SID> 9024 49 131200 21544960
    5 saptools 8712 1 131072 540672
    6 saptempdb 8716 -32767 131328 540672
    Could you help me to change this status, please?
    Best Regards,
    Dani

    Hi,
    After several attempts we have removed the suspect status but when restart the following appears:
    Database '<SID>', checkpoint=(1645024, 14), first=(155850, 0), last=(1648828, 149).
    Completed estimating recovery log boundaries for database '<SID>'.
    Started ANALYSIS pass for database '<SID>'.
    Completed ANALYSIS pass for database '<SID>'.
    Log contains all committed transactions until 2014/08/19 12:14:39.13 for database <SID>.
    Started REDO pass for database '<SID>'. The total number of log records to process is 2584914.
    Redo pass for database '<SID>': 129245 records done (4%); 2455669 records left.
    Redo pass for database '<SID>': 258490 records done (9%); 2326424 records left.
    Redo pass for database '<SID>': 387735 records done (14%); 2197179 records left.
    Redo pass for database '<SID>': 516980 records done (19%); 2067934 records left.
    Redo pass for database '<SID>': 646225 records done (24%); 1938689 records left.
    Redo pass for database '<SID>': 775470 records done (29%); 1809444 records left.
    Redo pass for database '<SID>': 904715 records done (34%); 1680199 records left.
    Redo pass for database '<SID>': 1033960 records done (39%); 1550954 records left.
    Redo pass for database '<SID>': 1163205 records done (44%); 1421709 records left.
    Redo pass for database '<SID>': 1292450 records done (49%); 1292464 records left.
    Redo pass for database '<SID>': 1421695 records done (54%); 1163219 records left.
    Redo pass for database '<SID>': 1550940 records done (59%); 1033974 records left.
    Error: 3474, Severity: 21, State: 1
    During redo the page timestamp value is less than old timestamp from log. Page #=1447848, object id = 1208908893, page timestamp=0000 09dcde72. Log old timestamp=0000 0a24137c. Log record marker = (1645024, 0).
    Database '<SID>' (dbid 4): Recovery failed. Check the ASE errorlog for further information as to the cause.
    Recovery has restored the value of 'local async prefetch limit' for '128K' pool in 'default data cache' from '80' to 'DEFAULT'.
    Recovery has restored the value of 'local async prefetch limit' for '16K' pool in 'default data cache' from '80' to 'DEFAULT'.
    Recovery has restored the original size for '128K' pool and '16K' pool in 'default data cache'.
    Recovery complete.
    (Attached the complete log file)
    Best Regards and thank you for your help.

  • Sharepoint Crawler database went to emergency mode

    Hi,
    My SharePoint Crawl Database went on Suspect mode suddenly & now i need to bring on Online mode.
    For solving this issue, i Google on several sites & came across following steps,
    Steps:
    EXEC sp_resetstatus 'DBName';
    ALTER DATABASE DBName SET EMERGENCY
    DBCC checkdb('DBName')
    ALTER DATABASE DBName SET SINGLE_USER WITH ROLLBACK IMMEDIATE
    DBCC CheckDB ('DBName', REPAIR_ALLOW_DATA_LOSS)
    ALTER DATABASE DBName SET MULTI_USER
    DBCC CheckDB ('DBName')
    Now the problem is Step 1 & 2 completed successfully, but when i tried step 3 it is throwing me below error,
    Msg 945, Level 14, State 2, Line 1
    Database 'DBName' cannot be opened
    due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
    I am using the service account which has full rights on the server & through which the SQL Server 2012 was configured.
    Current status Database is in Emergency mode & I am stuck over there.
    Please help.
    Regards,
    Purvish Shah

    Hi Alberto,
    Thank for the reply.
    I updated the Database with the below query ,
    ALTER DATABASE [YourDB] SET SINGLE_USER;
    GO
    It completed successfully, but the database is still in the
    "Emergency mode".When i checked in the logs it says 
    Message
    Setting database option SINGLE_USER to ON for database 'DBName'.
    Regards,
    Purvish Shah

  • Life with end mode

    https://www.reddit.com/3cyli8/
    https://www.reddit.com/3cynlo/
    https://www.reddit.com/3cyp7n/
    https://www.reddit.com/3cyqb1/

    Hello Chris,
    Hello as per this  article
    http://support.microsoft.com/kb/926070/en-us
    This is by design when you are running DBCC CHECKDB and try to perform any operation which leads to snapshot being suspect such error comes.This error says that database snapshot which was created by DBCC CHECKDB got in suspect mode due to shrink operation
    you ran your Original DB might not be suspect .Its always advised to as minimum activity as possible when checkdb is in progress or run checkdb in application downtime.
    Checkdb creates snapshot of DB on same disk where it resides so its necessary to make sure enough space is there.
    Other option is if you have enterprise edition you can manually take snapshot of DB and pace it on differnt drive and run checkdb on that.
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers
    Specific in the link you sent: "
    Error message 926 indicates that the database is marked as suspect. This error message actually refers to the internal snapshot and not to the actual database. The status of the database is "online," and the database is functional.
    Not sure if my attempted shrinkfile caused this or not, but I think I'm good. Thanks!
    TIA, ChrisRDBA

  • Error message "suspected state."

    we are using windows nt & sql server.
    we are facing suspected mode error.

    Sometimes when you try to connect to your SQL database server, you may get your SQL database in suspect mode. At that point your database server would not
    allow you to access and perform any operation on it. Your database will accessible only when the database will be repaired. For fixing the problem you will have to use advanced SQL database recovery tool. 
    SQL server database can go in suspect mode for many reasons; some of them are given below:
    Improper shutdown of the database server
    Corruption of the database files
    Unavailable device files
    Unavailable database files
    Database resource used by operating system
    SQL Server incorrectly asserts free data page space when a row is inserted
    Read Complete article here:
    http://sql-server-recovery.blogspot.in/2010/10/repair-restore-sql-server-database-from.html

Maybe you are looking for