SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


How to solve the corrupted logfies issue


How to solve the corrupted logfies issue

Author
Message
New persopn
New persopn
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1693 Visits: 710
Hi All,

Here I am new to this. so i want to know how to solve the corrupted log file.
prettsons
prettsons
SSCarpal Tunnel
SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)

Group: General Forum Members
Points: 4427 Visits: 1475
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 :-)
New persopn
New persopn
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1693 Visits: 710
Thank You very much
karrylopez
karrylopez
Valued Member
Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)

Group: General Forum Members
Points: 54 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.
Robert Davis
Robert Davis
SSCoach
SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)

Group: General Forum Members
Points: 15581 Visits: 1671
prettsons (8/7/2012)
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


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
SQL Server Best Practices: SQL Server Best Practices
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring
Microsoft Certified Master: SQL Server, Data Platform MVP
Database Engineer at BlueMountain Capital Management
GilaMonster
GilaMonster
SSC Guru
SSC Guru (549K reputation)SSC Guru (549K reputation)SSC Guru (549K reputation)SSC Guru (549K reputation)SSC Guru (549K reputation)SSC Guru (549K reputation)SSC Guru (549K reputation)SSC Guru (549K reputation)

Group: General Forum Members
Points: 549019 Visits: 47741
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, 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


db_expert_pradeep
db_expert_pradeep
SSC-Enthusiastic
SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)

Group: General Forum Members
Points: 128 Visits: 560
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search