Database "Suspect"

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
Hi
Tibor Karaszi has very good article about this issue.
http://www.karaszi.com/sqlserver/default.asp
"FLX" <nospam@.hotmail.com> wrote in message
news:Olmb3%23pjEHA.3876@.TK2MSFTNGP15.phx.gbl...
> 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
>
>
>
>

Database "Suspect"

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,
LXHi
Tibor Karaszi has very good article about this issue.
http://www.karaszi.com/sqlserver/default.asp
"FLX" <nospam@.hotmail.com> wrote in message
news:Olmb3%23pjEHA.3876@.TK2MSFTNGP15.phx.gbl...
> 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
>
>
>
>|||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
>
>
>
>
>.
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0023_01C48E73.F0CAC3E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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
>
>
>
>
>
>
>
>
>.
>
--=_NextPart_000_0023_01C48E73.F0CAC3E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

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.
"..." wrote in message news:08f701c48ea2$fb=cb5730$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>>>>>>>>>.>

---

--=_NextPart_000_0023_01C48E73.F0CAC3E0--|||This is a multi-part message in MIME format.
--=_NextPart_000_000A_01C48E96.A5005EC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Exactly! That is my problem now. Here is error message:
I/O error (torn page) detected during read at offset 0x0000002979e000 in =file "c:\XXXXXX"
What should I do to fix it?
Thanks in advance,
LX
"Ryan Stonecipher [MSFT]" <ryanston@.online.microsoft.com> wrote in =message 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
>
>
>
>
>
>
>
>
>.
>
--=_NextPart_000_000A_01C48E96.A5005EC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Exactly! That is my problem now. Here =is error message:
I/O error (torn page) detected during =read at offset 0x0000002979e000 in file "c:\XXXXXX"
What should I do to fix =it?
Thanks in advance,
LX
"Ryan Stonecipher [MSFT]" wrote in message news:eUfSe6qjEHA.704@.T=K2MSFTNGP12.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.
"..." wrote in message news:08f701c48ea2$fb=cb5730$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>>>>>>>>>.>

---

--=_NextPart_000_000A_01C48E96.A5005EC0--|||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@.tk2msftngp13.phx.gbl...
Exactly! That is my problem now. Here is error message:
I/O error (torn page) detected during read at offset 0x0000002979e000 in file "c:\XXXXXX"
What should I do to fix it?
Thanks in advance,
LX
"Ryan Stonecipher [MSFT]" <ryanston@.online.microsoft.com> wrote in message
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
>
>
>
>
>
>
>
>
>.
>

Database "Suspect"

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,
LXHi
Tibor Karaszi has very good article about this issue.
http://www.karaszi.com/sqlserver/default.asp
"FLX" <nospam@.hotmail.com> wrote in message
news:Olmb3%23pjEHA.3876@.TK2MSFTNGP15.phx.gbl...
> 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
>
>
>
>

Databas recovery - Urgent...

i was trying to retsart mu Sql 2000 Server and one of my
database was marked suspect at start up
sp_resetstatus and restarting the server did not help me
So i detached the database - while detaching it did not
detach cleanly and it gave a msg database was uanble to
shutdown cleanly
Now when i am trying to re-attach the database using
CREATE DATABASE DCCTDG01
ON PRIMARY (FILENAME = 'k:\DCCTDG01\DCCTDG01.mdf')
FOR ATTACH
GO
i am getting this msg
Server: Msg 3624, Level 20, State 1, Line 1
Location:
p:\sql\ntdbms\storeng\drs\include\record.inl:1447
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 55
Process ID: 1316
Connection Broken
Can someone pls help me as i dont have readily accesible
backups
Thanks
SanjayHi Sanjay,
Any chance the physical database files were corrupted somehow? If so, a
restore from backup might be the only option.
HTH,
--
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Sanjay" <sanjayg@.hotmail.com> wrote in message
news:042601c39a85$7579cbb0$a401280a@.phx.gbl...
> i was trying to retsart mu Sql 2000 Server and one of my
> database was marked suspect at start up
> sp_resetstatus and restarting the server did not help me
> So i detached the database - while detaching it did not
> detach cleanly and it gave a msg database was uanble to
> shutdown cleanly
> Now when i am trying to re-attach the database using
> CREATE DATABASE DCCTDG01
> ON PRIMARY (FILENAME = 'k:\DCCTDG01\DCCTDG01.mdf')
> FOR ATTACH
> GO
> i am getting this msg
> Server: Msg 3624, Level 20, State 1, Line 1
> Location:
> p:\sql\ntdbms\storeng\drs\include\record.inl:1447
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 55
> Process ID: 1316
> Connection Broken
>
> Can someone pls help me as i dont have readily accesible
> backups
> Thanks
> Sanjay|||Last week there was a bulk copy to a table going on in
this database and the box hanged
When we restarted the box the K;\ (raid drive where all db
files reside) could not be recognized bcoz of some power
supply problems
This week finally we put in a new power supply and box has
started with k:\ showing up and rest of databases are fine
The only one marked suspect is this one to which BCP in
was going on while box crashed.
Is Torn Page detection that is causing the suspect'
what could have avoided this suspect status '
Sanjay
>--Original Message--
>Hi Sanjay,
>Any chance the physical database files were corrupted
somehow? If so, a
>restore from backup might be the only option.
>HTH,
>--
>Greg Low (MVP)
>MSDE Manager SQL Tools
>www.whitebearconsulting.com
>"Sanjay" <sanjayg@.hotmail.com> wrote in message
>news:042601c39a85$7579cbb0$a401280a@.phx.gbl...
>> i was trying to retsart mu Sql 2000 Server and one of my
>> database was marked suspect at start up
>> sp_resetstatus and restarting the server did not help me
>> So i detached the database - while detaching it did not
>> detach cleanly and it gave a msg database was uanble to
>> shutdown cleanly
>> Now when i am trying to re-attach the database using
>> CREATE DATABASE DCCTDG01
>> ON PRIMARY (FILENAME = 'k:\DCCTDG01\DCCTDG01.mdf')
>> FOR ATTACH
>> GO
>> i am getting this msg
>> Server: Msg 3624, Level 20, State 1, Line 1
>> Location:
>> p:\sql\ntdbms\storeng\drs\include\record.inl:1447
>> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
>> SPID: 55
>> Process ID: 1316
>> Connection Broken
>>
>> Can someone pls help me as i dont have readily accesible
>> backups
>> Thanks
>> Sanjay
>
>.
>|||Hi Sanjay,
The fact that the others were ok probably just means this database was the
unlucky victim at the time. If you have backups of it from before then, I'd
be suggesting using them, particularly if it's an urgent problem.
HTH,
--
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Sanjay" <sanjayg@.hotmail.com> wrote in message
news:066d01c39ac3$efddb310$a501280a@.phx.gbl...
> Last week there was a bulk copy to a table going on in
> this database and the box hanged
> When we restarted the box the K;\ (raid drive where all db
> files reside) could not be recognized bcoz of some power
> supply problems
> This week finally we put in a new power supply and box has
> started with k:\ showing up and rest of databases are fine
> The only one marked suspect is this one to which BCP in
> was going on while box crashed.
> Is Torn Page detection that is causing the suspect'
> what could have avoided this suspect status '
> Sanjay
>
> >--Original Message--
> >Hi Sanjay,
> >
> >Any chance the physical database files were corrupted
> somehow? If so, a
> >restore from backup might be the only option.
> >
> >HTH,
> >
> >--
> >Greg Low (MVP)
> >MSDE Manager SQL Tools
> >www.whitebearconsulting.com
> >
> >"Sanjay" <sanjayg@.hotmail.com> wrote in message
> >news:042601c39a85$7579cbb0$a401280a@.phx.gbl...
> >> i was trying to retsart mu Sql 2000 Server and one of my
> >> database was marked suspect at start up
> >>
> >> sp_resetstatus and restarting the server did not help me
> >>
> >> So i detached the database - while detaching it did not
> >> detach cleanly and it gave a msg database was uanble to
> >> shutdown cleanly
> >>
> >> Now when i am trying to re-attach the database using
> >>
> >> CREATE DATABASE DCCTDG01
> >> ON PRIMARY (FILENAME = 'k:\DCCTDG01\DCCTDG01.mdf')
> >> FOR ATTACH
> >> GO
> >>
> >> i am getting this msg
> >>
> >> Server: Msg 3624, Level 20, State 1, Line 1
> >>
> >> Location:
> >> p:\sql\ntdbms\storeng\drs\include\record.inl:1447
> >> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> >> SPID: 55
> >> Process ID: 1316
> >>
> >> Connection Broken
> >>
> >>
> >> Can someone pls help me as i dont have readily accesible
> >> backups
> >>
> >> Thanks
> >> Sanjay
> >
> >
> >.
> >