Database "Suspect"

Try dettach + attaching the database...
>--Original Message--
>For whatever reason, I have a database marked
as "Suspect". I didn't find
>any clue from the error log. The drive has plenty of
free spaces. I don't
>have the backup files. Any suggestion to recover?
>Thanks a lot,
>LX
>
>
>
>
>.
>Detaching a suspect database can lead to big problems, especially since you
cannot attach a corrupt database. If the database is suspect because of rec
overy failures, and you try to attach it again, the attach command will fail
.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"..." <anonymous@.discussions.microsoft.com> wrote in message news:08f701c48
ea2$fbcb5730$a401280a@.phx.gbl...
Try dettach + attaching the database...
>--Original Message--
>For whatever reason, I have a database marked
as "Suspect". I didn't find
>any clue from the error log. The drive has plenty of
free spaces. I don't
>have the backup files. Any suggestion to recover?
>Thanks a lot,
>LX
>
>
>
>
>.
>|||Exactly! That is my problem now. Here is error message:
I/O error (torn page) detected during read at offset 0x0000002979e000 in fil
e "c:\XXXXXX"
What should I do to fix it?
Thanks in advance,
LX
"Ryan Stonecipher [MSFT]" <ryanston@.online.microsoft.com> wrote in messa
ge news:eUfSe6qjEHA.704@.TK2MSFTNGP12.phx.gbl...
Detaching a suspect database can lead to big problems, especially since you
cannot attach a corrupt database. If the database is suspect because of rec
overy failures, and you try to attach it again, the attach command will fail
.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"..." <anonymous@.discussions.microsoft.com> wrote in message news:08f701c48
ea2$fbcb5730$a401280a@.phx.gbl...
Try dettach + attaching the database...
>--Original Message--
>For whatever reason, I have a database marked
as "Suspect". I didn't find
>any clue from the error log. The drive has plenty of
free spaces. I don't
>have the backup files. Any suggestion to recover?
>Thanks a lot,
>LX
>
>
>
>
>.
>|||As I remember, the repair will remove the torn page, and all that depends on
it. I.e., you never
know how much data you will lose. I strongly encourage you to either restore
from a healthy backup,
or open a case with MS Support.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"FLX" <nospam@.hotmail.com> wrote in message news:%23rI67AsjEHA.556@.tk2msftng
p13.phx.gbl...
Exactly! That is my problem now. Here is error message:
I/O error (torn page) detected during read at offset 0x0000002979e000 in fil
e "c:\XXXXXX"
What should I do to fix it?
Thanks in advance,
LX
"Ryan Stonecipher [MSFT]" <ryanston@.online.microsoft.com> wrote in messa
ge
news:eUfSe6qjEHA.704@.TK2MSFTNGP12.phx.gbl...
Detaching a suspect database can lead to big problems, especially since you
cannot attach a
corrupt database. If the database is suspect because of recovery failures,
and you try to attach it
again, the attach command will fail.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"..." <anonymous@.discussions.microsoft.com> wrote in message
news:08f701c48ea2$fbcb5730$a401280a@.phx.gbl...
Try dettach + attaching the database...
>--Original Message--
>For whatever reason, I have a database marked
as "Suspect". I didn't find
>any clue from the error log. The drive has plenty of
free spaces. I don't
>have the backup files. Any suggestion to recover?
>Thanks a lot,
>LX
>
>
>
>
>.
>