Repair Database

  • Hi All!!

    How to repair sql server 2005 database ?

    Is it get repaired fully without any data loss ??

    Thanks.

  • Depends what's wrong

    Please run this and post the full results:

    DBCC CHECKDB (< Database Name > ) WITH NO_INFOMSGS, ALL_ERRORMSGS

    Do you have a clean backup?

    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
  • "Commnd(s) completed successfully"

    This message comes.

    Right now my database is not corrupted but i want to start my live data on sql server.

    That continously users will be working on my application so as and when database gets corrupted i should be able to repair it immediately.

    Hence i am asking this.

  • Shukla (5/15/2009)


    "Commnd(s) completed successfully"

    This message comes.

    Right now my database is not corrupted but i want to start my live data on sql server.

    That continously users will be working on my application so as and when database gets corrupted i should be able to repair it immediately.

    Hence i am asking this.

    Why would users cause the database to be corrupted, it is rare occurence and is usually related to hardware failure.

    Rather than working out the best way to fix corruption, the best plan is to have a robust back-up strategy where you can restore to a working database without any data loss.

  • Shukla (5/15/2009)


    That continously users will be working on my application so as and when database gets corrupted i should be able to repair it immediately.

    Users don't cause database corruption. This isn't Access that we're talking about here. It is impossible for a user using normal SQL queries to cause database corruption. 99% of corruptions are hardware related, specifically IO subsytem.

    You should (just as everyone should) run CHECKDB regularly to make sure there are no problems. If there are, fixing depends completely on the error. Take a look at this article. http://www.sqlservercentral.com/articles/65804/

    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