Problems attaching a SQL 2000 database

I have a customer that is trying to attach a SQL 2000
database into SQL Server 2000. I have tried Enterprise
Manager (Attach Db), T-SQL "sp_attach_db "
and "sp_attach_single_file_db" without success. I keep
on getting a errors like the ones shown in this snippet
from the SQLERRORLOG:
2003-12-10 10:00:58.79 spid51 SQL Server Assertion:
File: <p:\sql\ntdbms\storeng\drs\include\record.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
2003-12-10 10:00:58.79 spid51 Error: 3624, Severity:
20, State: 1.
2003-12-10 10:00:58.79 spid51 Error: 3313, Severity:
21, State: 2
2003-12-10 10:00:58.79 spid51 Error while redoing
logged operation in database 'MYDATABASE'. Error at log
record ID (84983:2649:335)..
2003-12-10 10:00:59.27 spid51 Error: 9004, Severity:
23, State: 7
The client does not have a backup :o(. Does anyone know
how I can recover from this situation? A repair option
would be much appreciated.
Thanks,
BobIt is time to call MS PSS... Sorry
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Bob" <bob.albert@.quest.com> wrote in message
news:088401c3bffe$1ebd59b0$a001280a@.phx.gbl...
> I have a customer that is trying to attach a SQL 2000
> database into SQL Server 2000. I have tried Enterprise
> Manager (Attach Db), T-SQL "sp_attach_db "
> and "sp_attach_single_file_db" without success. I keep
> on getting a errors like the ones shown in this snippet
> from the SQLERRORLOG:
> 2003-12-10 10:00:58.79 spid51 SQL Server Assertion:
> File: <p:\sql\ntdbms\storeng\drs\include\record.inl>,
> line=1447
> Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <=> MAXDATAROW'.
> 2003-12-10 10:00:58.79 spid51 Error: 3624, Severity:
> 20, State: 1.
> 2003-12-10 10:00:58.79 spid51 Error: 3313, Severity:
> 21, State: 2
> 2003-12-10 10:00:58.79 spid51 Error while redoing
> logged operation in database 'MYDATABASE'. Error at log
> record ID (84983:2649:335)..
> 2003-12-10 10:00:59.27 spid51 Error: 9004, Severity:
> 23, State: 7
> The client does not have a backup :o(. Does anyone know
> how I can recover from this situation? A repair option
> would be much appreciated.
> Thanks,
> Bob|||Thanks Wayne,
I guess I'll have to do just that!
Bob
>--Original Message--
>It is time to call MS PSS... Sorry
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Computer Education Services Corporation (CESC),
Charlotte, NC
>www.computeredservices.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"Bob" <bob.albert@.quest.com> wrote in message
>news:088401c3bffe$1ebd59b0$a001280a@.phx.gbl...
>> I have a customer that is trying to attach a SQL 2000
>> database into SQL Server 2000. I have tried Enterprise
>> Manager (Attach Db), T-SQL "sp_attach_db "
>> and "sp_attach_single_file_db" without success. I keep
>> on getting a errors like the ones shown in this snippet
>> from the SQLERRORLOG:
>> 2003-12-10 10:00:58.79 spid51 SQL Server Assertion:
>> File: <p:\sql\ntdbms\storeng\drs\include\record.inl>,
>> line=1447
>> Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <=>> MAXDATAROW'.
>> 2003-12-10 10:00:58.79 spid51 Error: 3624, Severity:
>> 20, State: 1.
>> 2003-12-10 10:00:58.79 spid51 Error: 3313, Severity:
>> 21, State: 2
>> 2003-12-10 10:00:58.79 spid51 Error while redoing
>> logged operation in database 'MYDATABASE'. Error at log
>> record ID (84983:2649:335)..
>> 2003-12-10 10:00:59.27 spid51 Error: 9004, Severity:
>> 23, State: 7
>> The client does not have a backup :o(. Does anyone
know
>> how I can recover from this situation? A repair option
>> would be much appreciated.
>> Thanks,
>> Bob
>
>.
>