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
> >
> >
> >.
> >
