repairing damaged sql server MDF and LDF files

Hi All,
My SQL server's data files all corrupted during a severe power failure, we m
anage to get back the data files and reinstall the sql server. but unforunat
ely we failed to attaching the database back to the server. The error messag
e indicating it is caused b
y corrupted MDF or LDF files.
Is there a way to perform a file level repair before we can attach it back t
o sql server again ?
Any help is very much appreciated.
Bernard GhHi,
Can you post the error you are getting while attaching the database.
If the MDF file is corrupted you have to either contact Microsoft product
support or restore from a valid full backup and restore the subsequent
transaction log backups in sequence.
Note:
During this situation even if you recover the database data integrity will
be lost. I recommend you to restore from full backup.
Thanks
Hari
MCDBA
"SummerCoke" <SummerCoke@.discussions.microsoft.com> wrote in message
news:C9AE06CD-460C-48C6-8510-4E1C1858FAE9@.microsoft.com...
> Hi All,
> My SQL server's data files all corrupted during a severe power failure, we
manage to get back the data files and reinstall the sql server. but
unforunately we failed to attaching the database back to the server. The
error message indicating it is caused by corrupted MDF or LDF files.
> Is there a way to perform a file level repair before we can attach it back
to sql server again ?
> Any help is very much appreciated.
> Bernard Gh|||I have been in the same situation with customers before. This is why you
have a fault tolerant RAID set(5, 1, 10, or 0+1), use Log Shipping and have
good backup plans. Sometimes things break and you don't get to piece them
together.
We often use a secondary IDE drive that the SCSI drives only dump
transaction backups to every 2-5 minutes. Hence, if the power goes out 1.)
the controller should have an onboard battery to complete the write or fail
it, 2.) we are never more than 2 minutes from the last 'good' state.
Plan for failure, because it will come:wether hardware, software or
intrusion.
Sorry,
Tim
"SummerCoke" <SummerCoke@.discussions.microsoft.com> wrote in message
news:C9AE06CD-460C-48C6-8510-4E1C1858FAE9@.microsoft.com...
> Hi All,
> My SQL server's data files all corrupted during a severe power failure, we
manage to get back the data files and reinstall the sql server. but
unforunately we failed to attaching the database back to the server. The
error message indicating it is caused by corrupted MDF or LDF files.
> Is there a way to perform a file level repair before we can attach it back
to sql server again ?
> Any help is very much appreciated.
> Bernard Gh|||with
EXEC sp_attach_db @.dbname = N'IMISWEB_OTHER',
@.filename1 = N'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWEB_OTHE
R_Data.MDF',
@.filename2 = N'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWEB_OTHE
R_LOG.LDF'
I got following:
Server: Msg 5172, Level 16, State 15, Line 1
The header for file 'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWE
B_OTHER_LOG.LDF' is not a valid database file header. The PageAudit property
is incorrect.
With
EXEC sp_attach_single_file_db @.dbname = 'IMISWEB_OTHER',
@.physname = 'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWEB_OTHER_
Data.MDF'
I got the following:
Server: Msg 5172, Level 16, State 15, Line 1
The header for file 'K:\Program Files\Microsoft SQL Server\MSSQL\data\IMISWE
B_OTHER_Log.LDF' is not a valid database file header. The PageAudit property
is incorrect.
Server: Msg 5170, Level 16, State 1, Line 1
Cannot create file 'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWEB
_OTHER_log.LDF' because it already exists.
Server: Msg 1813, Level 16, State 1, Line 1
Could not open new database 'IMISWEB_OTHER'. CREATE DATABASE is aborted.
Device activation error. The physical file name 'K:\Program Files\Microsoft
SQL Server\MSSQL\data\IMISWEB_OTHER_Log.LDF' may be incorrect.
Bernard goh
"Hari Prasad" wrote:

> Hi,
> Can you post the error you are getting while attaching the database.
> If the MDF file is corrupted you have to either contact Microsoft product
> support or restore from a valid full backup and restore the subsequent
> transaction log backups in sequence.
>
> Note:
> During this situation even if you recover the database data integrity will
> be lost. I recommend you to restore from full backup.
> Thanks
> Hari
> MCDBA
>
> "SummerCoke" <SummerCoke@.discussions.microsoft.com> wrote in message
> news:C9AE06CD-460C-48C6-8510-4E1C1858FAE9@.microsoft.com...
> manage to get back the data files and reinstall the sql server. but
> unforunately we failed to attaching the database back to the server. The
> error message indicating it is caused by corrupted MDF or LDF files.
> to sql server again ?
>
>