How to solve the corrupted logfies issue

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » Data Corruption (SS2K8 / SS2K8 R2) » How to solve the corrupted logfies issue

How to solve the corrupted logfies issue

Rate Topic

Display Mode

Topic Options

Author

Message

New persopn

Posted Tuesday, August 07, 2012 9:31 PM

Valued Member

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 12:56 AM
Points: 56, Visits: 163

Hi All,

Here I am new to this. so i want to know how to solve the corrupted log file.

Post #1341666

prettsons

Posted Tuesday, August 07, 2012 10:55 PM

SSC Journeyman

Group: General Forum Members
Last Login: 2 days ago @ 12:17 AM
Points: 99, Visits: 1,023

Do you have backup??
If you don't have backup then there is only one way to resolve log file corruption that is to rebuild log file. Check this article, it will help you to handle log file corruption: http://www.recoverdatabase.blogspot.com/2012/07/how-to-deal-with-log-file-corruption.html

SQL Database Recovery Expert Smile

Post #1341673

New persopn

Posted Wednesday, August 08, 2012 12:46 AM

Valued Member

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 12:56 AM
Points: 56, Visits: 163

Thank You very much

Post #1341697

karrylopez

Posted Friday, August 31, 2012 3:28 AM

Forum Newbie

Group: General Forum Members
Last Login: Friday, April 05, 2013 4:48 AM
Points: 4, Visits: 2

For your Log File corruption you can use restore this if you have backup and it also necessary that your backup have all the data which you required.

If you not have any backup so corrupt log file should be restored with help of any third party data recovery software just link Kernel for SQL Server. you can use this software for your corrupted log file.

Post #1352661

Robert Davis

Posted Monday, September 03, 2012 8:59 AM

SSCommitted

Group: General Forum Members
Last Login: Wednesday, May 15, 2013 7:57 PM
Points: 1,558, Visits: 1,395

prettsons (8/7/2012)

You should delete that blog post. That is very, very bad advice. You should NEVER detach a corrupted database. It is very likely that the database won't be able to shut down cleanly and then the database won't be able to be reattached and now instead of having just a corrupted log file, you will have lost the entire database.

Read this article by Paul Randal: http://www.sqlskills.com/BLOGS/PAUL/post/TechEd-Demo-Creating-detaching-re-attaching-and-fixing-a-suspect-database.aspx

My blog: SQL Soldier
Twitter: @SQLSoldier
Microsoft Certified Master: SQL Server 2008
Sr. Product Consultant and Chief SQL Server Evangelist @ Idera
My book: Pro SQL Server 2008 Mirroring

Post #1353570

GilaMonster

Posted Monday, September 03, 2012 9:06 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 2:48 AM
Points: 37,635, Visits: 29,886

Never, never, never, never detach a corrupt or suspect database. It will not help and it is very likely to make matters far worse.
Take a look at this article. http://www.sqlservercentral.com/articles/65804/

As for the DB with the corrupted log, if you have a good backup, restore it. If the DB is in full recovery and you have scheduled log you'll be able to restore with minimal data loss.
If you don't have a backup, you're in a world of hurt... I hope that's not the case.

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1353574

db_expert_pradeep

Posted Thursday, September 06, 2012 2:24 AM

Grasshopper

Group: General Forum Members
Last Login: Wednesday, April 17, 2013 12:24 AM
Points: 18, Visits: 377

I also agree with that never go for detach option if database is in suspected mode it will make situation more worse.
You can rebuild new log file if there is no option left.

Post #1355106

« Prev Topic | Next Topic »

Permissions