Error 823: I/O error (torn page)

  • Hi, can anyone help me on this? It all started when we had a power shortage. Eventually my server shutdown. Then I restarted it. I noticed that my database was already marked suspect. Then I tried to detach then attach the database in the hope that it will regain its normal state. However I could not attach it anymore and it shows Error 823: I/O error (torn page). Please advice me on this.

  • dominicgurat (11/4/2009)


    Hi, can anyone help me on this? It all started when we had a power shortage. Eventually my server shutdown. Then I restarted it. I noticed that my database was already marked suspect. Then I tried to detach then attach the database in the hope that it will regain its normal state. However I could not attach it anymore and it shows Error 823: I/O error (torn page). Please advice me on this.

    You shouldnt have detached it, but you know that now...

    Have you got any backups

    --------------------------------------------------------------------------------------
    [highlight]Recommended Articles on How to help us help you and[/highlight]
    [highlight]solve commonly asked questions[/highlight]

    Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
    Managing Transaction Logs by Gail Shaw[/url]
    How to post Performance problems by Gail Shaw[/url]
    Help, my database is corrupt. Now what? by Gail Shaw[/url]

  • Unfortunately the only backup i have is two to three weeks ago. Any hope that I can regain my data? Please help solve this. Thank you in advance

  • dominicgurat (11/4/2009)


    Unfortunately the only backup i have is two to three weeks ago. Any hope that I can regain my data? Please help solve this. Thank you in advance

    sigh, not sure what to say to you, if the database was still atttached, there are things you can do to fix the suspect state.

    try this

    create a new database called y for example

    stop the sql services

    copy the suspect database files over the new database files

    restart the sql services.

    and hopefully the database will come back up.

    if that works, let me know and I can show you how to fix the supect state if it is still there.

    You will need to rename the old database filenames to the new files that you are replacing, so the master entry is the same.

    If you need clarification on anything let me know

    --------------------------------------------------------------------------------------
    [highlight]Recommended Articles on How to help us help you and[/highlight]
    [highlight]solve commonly asked questions[/highlight]

    Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
    Managing Transaction Logs by Gail Shaw[/url]
    How to post Performance problems by Gail Shaw[/url]
    Help, my database is corrupt. Now what? by Gail Shaw[/url]

  • See TechEd Demo: Creating, detaching, re-attaching, and fixing a suspect database for complete instructions.

    Paul Randal
    CEO, SQLskills.com: Check out SQLskills online training!
    Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
    SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
    Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

  • Very nice article Paul, pretty much the same as what I suggested but in a nicer format. and pretty fonts and colours. 😛

    Thanks for the link, hopefully the op will appreciate it as much as I did reading it.

    --------------------------------------------------------------------------------------
    [highlight]Recommended Articles on How to help us help you and[/highlight]
    [highlight]solve commonly asked questions[/highlight]

    Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
    Managing Transaction Logs by Gail Shaw[/url]
    How to post Performance problems by Gail Shaw[/url]
    Help, my database is corrupt. Now what? by Gail Shaw[/url]

  • Hi,

    I am facing an 823 problem (TORN PAGE) The database is in suspect state. Can you please guide me towards restoring the corrupt file.

    Thanks in advance

  • Please post your question in a new thread, put it in the correct corruption forum for the version of SQL that you have and include the output of the following command if possible.

    DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

    Thank you

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply