Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-01-15 : 14:54:35
|
| Shirley writes "We have a 2.6GB database. Suddenly it is found that there are 26 consistency errors after running the DBCC CheckDB statement.We have run the repair statement of Repair_Fat, Repair_Rebuild and Repair_Allow_Data_Loss. After all these action, indeed, the quantity of consistency errors increases.Too bad that our valid backup which have no DBCC CheckDB is back to Oct 31.Instead of restoring the backup. What can we do ?" |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-01-15 : 18:03:24
|
| You are going to have to export the data, rebuild the database schema, then import the data back in. After you have the database back up and running, schedule your backups to occur at least daily and integrity checks to occur at least once a week. |
 |
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2003-01-15 : 20:47:56
|
| Also check your disks. Torn pages are caused by incomplete writes of a SQL data page to physical disk. If you have a write cache on a disk controller make sure it has a battery backup and also makes sure the server itself has a UPS.HTHJasper Smith |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-01-16 : 00:38:42
|
quote:
Also check your disks.
Very good point! |
|
|
|
Argyle
Yak Posting Veteran
53 Posts |
Posted - 2003-01-16 : 03:51:42
|
| If you have transaction log backups I would use the healthy full backup that you have from Oct 31 that is consistent (doesn't report errors from dbcc checkdb). Then I would restore it on a healthy system and restore all transactions log up to the current date (skip any full backups between).That way you will rerun all transactions on this healthy system and you most likely end up with a healthy database again. I've done that a couple of times.After that you should check what is causing the error in the first place. Could be disk issues. That's been the reason when I had consistency errors. Then we have reinstalled the original system or replaced disks before moving back the healthy database to production again./ArgyleEdited by - argyle on 01/16/2003 03:52:30 |
|
|
|
|
|
|
Torn Page