dbcc checkdb(‘DB-NAME’,REPAIR_ALLOW_DATA_LOSS) didnt fix the issue

  • I ran dbcc checkdb(‘DB-NAME’,REPAIR_ALLOW_DATA_LOSS) and it didnt fix the inconsistencies.

    Now, I may need to restore the backup from the previous full backup.

    But my question is, will the backup file not have these inconsistency errors?

  • Same database had got corrupted a fortnight back and dbcc checkdb(‘DB-NAME’,REPAIR_ALLOW_DATA_LOSS) did fix the inconsistencies.

    I also see a stack dump which has got generated in SQL Server error logs.

  • Please don't x-post.

    This post has already been replied to: http://www.sqlservercentral.com/Forums/Topic1488317-391-1.aspx

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • If your last checkdb fixed the data consistency errors and you took a full backup afterwards, that backup would be good (albeit, you may be missing some data). If no backup was taken then you will have the same errors and will need to run a checkdb with repair, allow data loss again.

    ______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience

  • MyDoggieJessie (9/9/2013)


    If your last checkdb fixed the data consistency errors and you took a full backup afterwards, that backup would be good (albeit, you may be missing some data). If no backup was taken then you will have the same errors and will need to run a checkdb with repair, allow data loss again.

    No, please, no. Repair is not and should never be the first thing considered or suggested.

    Also, if you read the thread he originally started, the checkDB did not repair everything.

    Please, can we keep the discussion on the original thread?

    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

Viewing 5 posts - 1 through 4 (of 4 total)

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