Re: URGENT : Error Message 823 - bad page id

From: alaspin (alaspin_at_yahoo.com)
Date: 06/18/03 

Date: Wed, 18 Jun 2003 05:42:10 -0700

woohoo!

Well - nearly. Thanks Herbert...

>-----Original Message-----
>Try DBCC CHECKDB. This has a repairfunction, too.
>
>best regards,
>Herbert Albert
>
>"alaspin" <alaspin@yahoo.com> schrieb im Newsbeitrag
>news:041901c33582$b9c0d970$a001280a@phx.gbl...
>> OK, this is what I've just been given:
>>
>> Catastrophic HDD failure has led me to attach a
>> recovered .mdf file into a clean install of SQL Server
>> 2000. There was no backup available (please DON'T ask
why)
>> and so the data was recovered.
>>
>> I have run "SELECT * FROM X" on all the non-system
tables
>> and discovered that only one comes back with errors
>> (phew!). I am not discounting the possibility that those
>> tables that look OK might have affected data BUT the
major
>> problem is:
>>
>> Server Msg 823, Level 24, State2, Line 1
>> I/O error (bad page ID) detected during read at offset
>> 0x00000001fc0000 in file 'C:\Program Files\Microsoft SQL
>> Server\MSSQL\Data\RMS_Data.MDF'.
>>
>> on one of the tables. My understanding of SQL Server
table
>> storage is that data is stored in pages and that these
>> pages are linked (a bit like a linked list). Apparently
>> this message is telling me that one of the links is
>> broken/cannot be resolved.
>>
>> Q. Is there aything I can do about this?
>>
>> Or are the users with no adequate backup strategy going
to
>> learn from their mistake? :)
>>
>> Any help appreciated...
>>
>> alaspin@yahoo.com
>>
>
>
>.
>

Quantcast