Post reply

How to solve the corrupted logfies issue

  • August 7, 2012 at 9:31 pm

    #262441

    Hi All,

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

  • August 7, 2012 at 10:55 pm

    This was removed by the editor as SPAM

  • August 8, 2012 at 12:46 am

    #1522972

    Thank You very much

  • August 31, 2012 at 3:28 am

    #1532267

    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.

  • September 3, 2012 at 8:59 am

    #1533006

    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[/url]
    SQL Server Best Practices:     SQL Server Best Practices
    Twitter: @SQLSoldier
    My book: Pro SQL Server 2008 Mirroring[/url]
    Microsoft Certified Master: SQL Server, Data Platform MVP
    Database Engineer at BlueMountain Capital Management[/url]

  • September 3, 2012 at 9:06 am

    #1533010

    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

  • September 6, 2012 at 2:24 am

    #1534293

    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.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply