Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
chaithanya
Starting Member
17 Posts |
 Posted - 2004-10-12 : 08:26:31
|
| hi all,one of my databases 'common' went into suspect mode. i tried to reset the status by executing sp_resetstatus that threw me the following message.Prior to updating sysdatabases entry for database 'common', mode = 0 and status = 1077936152 (status suspect_bit = 0).No row in sysdatabases was updated because mode and status are already correctly reset. No error and no changes made.any idea, plz?chaithanya J |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2004-10-12 : 08:35:44
|
| Have you restarted SQL Server yet? |
 |
|
|
chaithanya
Starting Member
17 Posts |
Posted - 2004-10-12 : 09:09:52
|
| yes Robvolk, thank you it worked.chaithanya J |
|
|
|
sify
Starting Member
18 Posts |
Posted - 2004-10-12 : 23:03:56
|
| Also if your server can not be restarted then attach and detach the database files. So the other users to the server will not be disconntected.Also check if the Auto Close option for the database is turned on. At times during Auto Close and Opening of the file the link between the database name and the physical file name gets disconnected and thus the database enters in suspect mode. |
|
|
|
|
|
|
suspect mode