Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Can anyone give me a complete guide to verifying/repairing a SQL Server database?

At the moment our backup is failing on the Solarwinds database saying the database NetPerfMon is corrupted (we are using Backup Exec 12.5 to perform the backups). I have SQL Server 2005 Management Studio Express installed if that helps other than that I don't have much of an idea what to do with SQL other than little bits of dabbling with it.

share|improve this question

closed as too broad by Mark Storey-Smith, Paul White, Max Vernon, ypercubeᵀᴹ, RolandoMySQLDBA Jul 15 '14 at 15:15

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

You can refer to Gail's excellent doc Help, my database is corrupt. Now what? – Kin Jul 14 '14 at 15:02

Please run below command in your SQL server database to check the level of corruption.If database is showing suspect it wont allow you to run this command


This command can be used to check corruption in SQL Server database. Also I must say you are running very old version of SQL server if you are not on SP4 your SQL server is in un supported state. If above command returns any consisteny and allocation error there is corruption in SQL server database if not then issue is with backup tool you need to contact vendor in that case.

Best method to recover from corruption is to restore from latest valid backup. You can use RESTORE VERIFYONLY to check consistency of backup before restoring although only successful restore can guarantee that backup is in complete consistent state.

Your other task is to look at SQL Server errrorlog and windows event viewer to find any information related to corruption and take appropriate action. Major cause is inconsistent disk subsystem.

Restoring from valid backup would involve first restoring full backup with no recovery then differential backup(if any) with no recovery and then all log backup witn no recovery but the last log backup with recovery.I you just have full database backup you can restore it with recovery.

How to restore database using SSMS

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.