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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2002-01-01 : 23:31:06
|
| Nirac writes "Hi,I am using Enterprise and Desktop additions of the MS SQL Server - 7. Many times myself and few of our clients are facing error of database suspect. Though I know one of the reason of database suspect is lake of space on harddrive, I check that option. But the problem of suspect is due to some other reason. So I can not resolve that problem and even not able to know the reason to make database suspect. The only thing I can do on those database is to delete it and resotore the last taken backup.So please send me the list of reasons which can cause database suspect and how I can turn it to normal one.Waiting for reply,RegardsNirav Patel" |
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2002-01-03 : 14:03:30
|
| Nirav,We have had several discussions on suspect databases and how to recover them. I would suggest that, in addition to reading up on the topic in SQL Server Books Online, that you also do a Forum Search here at SQLTeam on the words "suspect database" and review those threads.--------------------------------------------------------------1000 Posts, Here I come! I wonder what my new title will be... |
 |
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2002-01-04 : 11:03:00
|
| Try this...//If your have a database that is marked suspect but there is no real //problem this script will change the status flag and allow you to use//the database. If you have more than one suspect database, comment//the shutdown database section until you have changed the status on//all suspect databases.use mastergosp_configure "allow updates", 1reconfigure with overridegoupdate sysdatabasesset status = status - 256where name = "database name"and status & 256 = 256gosp_configure "allow updates", 0reconfiguregocheckpointgoshutdowngo |
 |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-01-04 : 19:24:07
|
| There are many reasons that a database can be suspect, and I don't believe any such 'List' exists.However, you can usually determine the reson by looking at the errorlog the first time it is declared suspect. The errorlog is in the mssql7\log directory, and there will be an error number and description. Post this next time, and maybe someone will be able to tell you why it's suspect (Or maybe it will be obvious).-Chad |
 |
|
|
|
|
|
|
|