August 31, 2008 at 1:01 pm
Hi,
Do you have a tool to recover or repair corrupt SQL MDF database, I need to repair them or else a RAW recovery tool to recover the same
I have a RAID 5 Server whose RAID crushed and on its rebuilding and the server would boot ok, the database files i.e. the mdf/ ldf files came back as corrupted, the sql had 2 different databases one of 4gb and 13gb both of which are both corrupt.
Am in need of a good application that will repair the above without loosing any data there in
Kindly revert
George
August 31, 2008 at 1:13 pm
Restore a backup? Depending on the type of corruption the built-in SQL tools may be able to repair them, or may not. If not, it's unlikely that a 3rd party tool will be able to.
What's the output of the following for each of those databases?
DBCC CheckDB ('< Database Name > ') WITH NO_INFOMSGS
If the DBs are suspect, you'll have to switch them into energency mode first.
I assume you are on SQL 2000. If so, switching into emergency mode means enabling update of the system tables and setting the status of the suspect databases to 32768 in sysdatabases
NB. This is a last resort and not the first thing to try. If you have a backup, restore it. Updating the system tables is a risky thing to do and can do more damage than it fixes
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
August 31, 2008 at 1:41 pm
am not very good with sql, i wouldnt be confident to say i can do a thing or two
but i have tried attaching the files as i dont have a backup and i get this error
" Microsoft SQL Server Error: 5171 not a primary database file"
i have also tried creating another database with the same file name as the corrupt dbase, then i deleted the ldf and mdf of what i created and i have copied back my corrupt dbase there in on the sql folder
any chances here
August 31, 2008 at 1:50 pm
the idea of creating the same database under the name of my current database with is corrupt seem to have taken me to a new height
the database am assuming attached but now its listed as " suspect"
kindly explain how do i resolve this
how do i test/ examine / repair the database
you quoted i start sql in emergency mode, how is that done
any thing else i could do to resolve this ?
kindly revert
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply