How can i recover corrupted database file( .mdf .ldf).

  • I run MSDE on a Windows XP Server and my database was marked as "suspect" by Enterprise Manager and its icon become gray.

    I detach that database and try to re-attach it but there is an error as the following:

    Error 3624:

    Location : page.cpp:2801

    Expression: rowLength >= offset + deleteLenght

    SPID : 56

    Precess ID:1612

    After that, I uninstall the MSDE and re-install new MSDE SP4 and try to re-attach the database file again and there is still an error.

    Is there anyway i can recover the data from that database?

    Would appreciate your help

  • This was removed by the editor as SPAM

  • Chances are you've lost this database. You should never detach it or uninstall. You need to be able to examine the database when it's suspect.

    If you don't have backups, there isn't a good solution for you.

  • Restore from backup.

    And, just maybe, consider getting an OS and SQL version that's slightly more modern?

    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
  • This site can help you: http://www.filerepairforum.com/forum/microsoft/microsoft-aa/sql-server/569-i-have-a-problem-how-do-i-fix-a-corrupted-database-file

    -Determine which program is associated with the corrupted data by the error messages you are receiving. For example, if you consistently receive a "File Not Found" error when starting Microsoft Word, it is likely that the corrupted data is a Word file.

    -Reinstall a fresh version of the program which currently contains corrupted data. Insert the installation CD for the program into your computer's CD drive.

    -Double click on the "My Computer" link.

    -Double click on your CD drive letter (typically the "D" drive).

    -Click on the "Setup.exe" file contained there to begin the reinstallation process.

    -Select the option "Install/Reinstall" to reinstall the program. All of the files associated with the program will be patched over, fixing the corrupted data.

    See more: SQL Server Fix Toolbox

    http://www.fixsqldatabase.com/[/url]

  • To repair the corrupt, damaged SQL database make use of the best high-quality SQL Repair tool. This is the best tool to repair the damaged, corrupted SQL server database without any hassle. This is best to deal with any type of corruption and errors in SQL database.

    To know more visit: How to Recover Corrupt MS SQL Server Database

  • This was removed by the editor as SPAM

  • stephanictaylor - Tuesday, January 17, 2017 2:35 AM

    Hi,
    To recover the damaged data of SQL, first it needs to be repaired with proper software so that the database remains safe and after that you can recover the stored data from it. However to fix the corruption issue in sql server, one should use SQLMDF File Repair Tool. This is one of the best repair tool which repairs any kind errors in sql mdf.
    Know more on: http://www.filerepairtool.net/blog/recover-corrupt-mdf-ldf-files

    You're posting on a very old thread. Chances are, the OP is no longer looking at this.

    Also, using third party repair tools increases the chances of losing data in the files, so many of us don't recommend them.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • This is an old thread, but 
    1.  So the files do not become further corrupt, make a backup copy of the .mdf data and .ldf log files. This files should preferably be copied to removable media or a network folder, because the data drive itself may be going bad.
    2.  Install the latest version of SQL Server developer or trial edition (ex: today that would be 2016 SP1), and then attempt to mount the database file from it's original location. Hopefully, this will get your database to point where you take further corrective action. 
    3.  Go to SQLSkills and read up on latest advice for checking and fixing corruption.

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

  • This was removed by the editor as SPAM

  • This was removed by the editor as SPAM

Viewing 11 posts - 1 through 10 (of 10 total)

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