Solved

MSSQL 2000 - Error 823

Posted on 2004-10-07
7
356 Views
Last Modified: 2012-08-14
I am constantly getting the following error on one of my databases. This database drives a backup solution. The clients have been hanging during their backups since this error has started to occur. I am not sure how to solve it or where to begin so any help would be greatly appreciated.

Error: 823, Severity: 24, State: 2
I/O error (bad page ID) detected during read at offset 0x0000023d1a0000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\directory.mdf'.

Thank you,

Keith Hall
0
Comment
Question by:sandvine
7 Comments
 
LVL 21

Accepted Solution

by:
JestersGrind earned 168 total points
ID: 12252980
Hi Keith,

Sounds like your clients hard drive is going bad.  Check out the following article from Microsoft.

http://support.microsoft.com/default.aspx?scid=kb;en-us;828339

Hope this helps!

Greg

0
 
LVL 13

Assisted Solution

by:davidlars99
davidlars99 earned 166 total points
ID: 12255164
I don't really think that MS link will help, but let me explain what SQL means by (bad page ID). page recides in extent and every single record that you add it is kept in the page, so extent contains 8 pages if one of these page is damaged there is no way of repairing that database, but you can try

DBCC CHECKDB
    ( 'database_name'
            [ , NOINDEX
                | { REPAIR_ALLOW_DATA_LOSS
                    | REPAIR_FAST
                    | REPAIR_REBUILD
                    } ]
    )    [ WITH { [ ALL_ERRORMSGS ]
                    [ , [ NO_INFOMSGS ] ]
                    [ , [ TABLOCK ] ]
                    [ , [ ESTIMATEONLY ] ]
                    [ , [ PHYSICAL_ONLY ] ]
                    }
        ]

for more info open "SQL Server Book Online" and search for "DBCC CHECKDB"


0
 
LVL 34

Assisted Solution

by:arbert
arbert earned 166 total points
ID: 12256116
I agree with davidlars99.  Harddrive going bad could be a possibility, but I think it's probably not the case.

Be careful with CHECKDB, you can destroy what you do have using the rebuild options.  Do you have a good backup at all?  If not, I would suggestion you trying to export the data first (using DTS or insert into queries) before you do a CHECKDb....

Brett
0
 

Author Comment

by:sandvine
ID: 12514398
Unfortunately I ended up restoring from a backup. The database was on a failed hard drive and was too far gone to be repaired. Please split the points amongst all participants. Thank you.
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

The Delta outage: 650 cancelled flights, more than 1200 delayed flights, thousands of frustrated customers, tens of millions of dollars in damages – plus untold reputational damage to one of the world’s most trusted airlines. All due to a catastroph…
Ever wondered why sometimes your SQL Server is slow or unresponsive with connections spiking up but by the time you go in, all is well? The following article will show you how to install and configure a SQL job that will send you email alerts includ…
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now