Our default instance of SQL 2000 is corrupted. The msdb database
tables do not have several columns required by the SQL Agent. The
corruption apparently occurred while running the SQL Wizard to convert
our 6.5 version to 2000. TO rectify the problem we successfully
installed a new instance of SQL which gave us a clean set of msdb and
master tables. We then copied our user databases over to the new
instance. My question is this: can we now make that new instance the
default instance? How can we do this? Thanks.You can't rename an instance, backup/restore is the way to go (or some simil
ar thing). Before you do that,
script out the job definitions etc from the msdb database so you can run tho
se scripts in the dest db.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Jim" <jromano@.phs-us.com> wrote in message news:e1e1a687.0403241251.1c364809@.posting.googl
e.com...
> Our default instance of SQL 2000 is corrupted. The msdb database
> tables do not have several columns required by the SQL Agent. The
> corruption apparently occurred while running the SQL Wizard to convert
> our 6.5 version to 2000. TO rectify the problem we successfully
> installed a new instance of SQL which gave us a clean set of msdb and
> master tables. We then copied our user databases over to the new
> instance. My question is this: can we now make that new instance the
> default instance? How can we do this? Thanks.|||Hi ,
Add on to Tibor, Instead of moving the user databases to new named instance,
why dont you take a backup of MSDB database from the new
named instance and restore it in Default instance.
This is under the assumption only your MSDB has got issues. This case all
your Logins/Backup devices and configuration info in Master
database can be preserved.
Have a look into the below article (Just read the MSDB part only)
http://support.microsoft.com/defaul...b;EN-US;Q224071
If you have problems in detach/attach, try with backup and restore strategy.
Thanks
Hari
MCDBA
"Jim" <jromano@.phs-us.com> wrote in message
news:e1e1a687.0403241251.1c364809@.posting.google.com...
> Our default instance of SQL 2000 is corrupted. The msdb database
> tables do not have several columns required by the SQL Agent. The
> corruption apparently occurred while running the SQL Wizard to convert
> our 6.5 version to 2000. TO rectify the problem we successfully
> installed a new instance of SQL which gave us a clean set of msdb and
> master tables. We then copied our user databases over to the new
> instance. My question is this: can we now make that new instance the
> default instance? How can we do this? Thanks.
Showing posts with label corrupted. Show all posts
Showing posts with label corrupted. Show all posts
Friday, March 30, 2012
Wednesday, March 7, 2012
repairing damaged sql server MDF and LDF files
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 b
y 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
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...
> 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_OTHER_Data.MDF',
@.filename2 = N'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWEB_OTHER_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\IMISWEB_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\IMISWEB_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 ?
>
>
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 b
y 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
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...
> 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_OTHER_Data.MDF',
@.filename2 = N'K:\Program Files\Microsoft SQL Server\MSSQL\Data\IMISWEB_OTHER_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\IMISWEB_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\IMISWEB_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 ?
>
>
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 ?
>
>
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 ?
>
>
repairing damaged sql server MDF and LDF files
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 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|||I found this program on the web...we just had the same
thing happen and I wondered if anyone has used it (I
posted this as a topic)...it's called MSSQLRECOVERY 2.0
and can be found at www.mssqlrecovery.com
Kevin
>--Original Message--
>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
>.
>|||Hi there,
We have tried that, but the result isn't impressive for us (2 tables out of 20+), perhaps the corruption is too servere for our case. but you can try your luck.
what other program have you tried ?
--
Bernard goh
"Kevin" wrote:
> I found this program on the web...we just had the same
> thing happen and I wondered if anyone has used it (I
> posted this as a topic)...it's called MSSQLRECOVERY 2.0
> and can be found at www.mssqlrecovery.com
> Kevin
>
> >--Original Message--
> >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
> >.
> >
>
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 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|||I found this program on the web...we just had the same
thing happen and I wondered if anyone has used it (I
posted this as a topic)...it's called MSSQLRECOVERY 2.0
and can be found at www.mssqlrecovery.com
Kevin
>--Original Message--
>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
>.
>|||Hi there,
We have tried that, but the result isn't impressive for us (2 tables out of 20+), perhaps the corruption is too servere for our case. but you can try your luck.
what other program have you tried ?
--
Bernard goh
"Kevin" wrote:
> I found this program on the web...we just had the same
> thing happen and I wondered if anyone has used it (I
> posted this as a topic)...it's called MSSQLRECOVERY 2.0
> and can be found at www.mssqlrecovery.com
> Kevin
>
> >--Original Message--
> >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
> >.
> >
>
Repair Corrupted MDF & LDF Files ?
Hi All
I am looking for repair tools for corrupted mdf and ldf files,
( These files beeing corrupted after i restore them using Easy Recovery Profissional after formatting c drive by mistake. )
Remark : one file of my 3 databases work perfectly when i use attach database.
Any Help will Be appreciated.
thanks
What errors comes back while attaching the database ?HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
Repair an SQL Server 2005 installation.
Hi,
Some part of my system registry seens corrupted, and I can not run the report services configuration tool, it gave me the following error:
0x80010002: RCP_E_CALL_CANCELED
1) Does a repair of the installation will register back the COM Servers?
2) After a repair does the report services encription key will be affected.
My main problem is to perform a backup of the report services encription key on a server that is not very stable.
3) Is there another way to backup the encription key without using the report services configuration tool?
Thanks
JF
Hi, found my answers... and it solve my problem.
Performing a Windows 2003 Server repair (not repair console) has fix my registry problem and was able to connect back with the report services configuration tool.
Also I found the following cmd line to backup the encryption key: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\RSKeyMgmt.exe
Subscribe to:
Posts (Atom)