Error 823

Hello.
I pray to that someone can help me...
A month ago a compaq server hosting a SQL Server 2000 Server had a hardware
crash. Unfortunatly, the Compaq Smart Array was configured with RAID 0.
Aparently the problem was there a long time ago and there was not a recently
backup file. So, we've delivered the Raid System to a Recovery company.
The data was recovered, I have the .MDF and the .LDF files. The problem is,
after i attach the database to a clean instance of Sql Server, i get the
following error:
******************
Server: Msg 823, Level 24, State 2, Line 1
I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
file 'D:\Data\database_Data.MDF'.
Connection Broken
******************
I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
with no results.
How can I resove this problem? I have read thousands of Forum messages but
i've no solution. I have read Microsoft Knowledge Base Article 826433, that
tells me that there are a build of Sql server, wich have several tools to
try to correct this problem. Tha leads me to another problem... i cannot
find that file versions.
I would thanks any solution, any help.
Regards.
Marco Pais
You can't correct this error - its a hard error with the underlying disk
(i.e. the OS tells SQL Server it can't read the bytes off the disk). You'll
need to suck as much data out of the database as you can onto new media. I
would contact PSS to help you (http://support.microsoft.com)
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marco Pais" <mpais@.foruminformatica.pt> wrote in message
news:u34zmu2PEHA.2132@.TK2MSFTNGP11.phx.gbl...
> Hello.
> I pray to that someone can help me...
> A month ago a compaq server hosting a SQL Server 2000 Server had a
hardware
> crash. Unfortunatly, the Compaq Smart Array was configured with RAID 0.
> Aparently the problem was there a long time ago and there was not a
recently
> backup file. So, we've delivered the Raid System to a Recovery company.
> The data was recovered, I have the .MDF and the .LDF files. The problem
is,
> after i attach the database to a clean instance of Sql Server, i get the
> following error:
> ******************
> Server: Msg 823, Level 24, State 2, Line 1
> I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
> file 'D:\Data\database_Data.MDF'.
> Connection Broken
> ******************
> I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
> with no results.
> How can I resove this problem? I have read thousands of Forum messages but
> i've no solution. I have read Microsoft Knowledge Base Article 826433,
that
> tells me that there are a build of Sql server, wich have several tools to
> try to correct this problem. Tha leads me to another problem... i cannot
> find that file versions.
> I would thanks any solution, any help.
> Regards.
> Marco Pais
>
|||Hi...
I cannot extract much data out of the database and I can't view the most
important tables data. i get allways the same error.
I've tried to attach the database in a brand new computer, with a fresh
instance of SQL Server. The problem is in the .MDF file, i gess. Is there
any tool that repair (or try to) .MDF files?
Thanks again...
Regards
"Paul S Randal [MS]" <prandal@.online.microsoft.com> escreveu na mensagem
news:%234c1x02PEHA.640@.TK2MSFTNGP12.phx.gbl...
> You can't correct this error - its a hard error with the underlying disk
> (i.e. the OS tells SQL Server it can't read the bytes off the disk).
You'll
> need to suck as much data out of the database as you can onto new media. I
> would contact PSS to help you (http://support.microsoft.com)
> Regards.
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> "Marco Pais" <mpais@.foruminformatica.pt> wrote in message
> news:u34zmu2PEHA.2132@.TK2MSFTNGP11.phx.gbl...
> hardware
> recently
> is,
in[vbcol=seagreen]
but[vbcol=seagreen]
> that
to[vbcol=seagreen]
cannot
>
|||I suspect you're not going to get much out of this - why you should always
have a comprehensive, tested backup strategy.
I recommend calling PSS to help you (http://support.microsoft.com) as
there's nothing that can be done over the newsgroups.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marco Pais" <mpais@.foruminformatica.pt> wrote in message
news:#YeRze3PEHA.832@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Hi...
> I cannot extract much data out of the database and I can't view the most
> important tables data. i get allways the same error.
> I've tried to attach the database in a brand new computer, with a fresh
> instance of SQL Server. The problem is in the .MDF file, i gess. Is there
> any tool that repair (or try to) .MDF files?
> Thanks again...
> Regards
>
> "Paul S Randal [MS]" <prandal@.online.microsoft.com> escreveu na mensagem
> news:%234c1x02PEHA.640@.TK2MSFTNGP12.phx.gbl...
> You'll
I[vbcol=seagreen]
> rights.
0.[vbcol=seagreen]
company.[vbcol=seagreen]
problem[vbcol=seagreen]
the[vbcol=seagreen]
0x0000001ef3c000[vbcol=seagreen]
> in
far,
> but
> to
> cannot
>