DBCC CheckTable returns following results, best way to deal with this?

Question

DBCC CheckTable returns following results, best way to deal with this?

Viewing 7 posts - 16 through 21 (of 21 total)

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

Steve Jones - SSC Editor SSC Guru Points: 736063 More actions · Answer 1

I would move to different physical drives, but I'd also do diagnostics. Depending on your situation, you could have firmware/filter drivers (as Gail mentioned) causing issues.

These are strange, hard to pin down errors, but almost all the time they are related to hardware. Most of the hardware appears to work, which is what is frustrating.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 2

aurato (3/12/2013)
Would you recommend migrating the databases on this disk to a different drive?

Well, ask yourself, would you leave important information on a drive that's giving repeated problems?

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

aurato SSCrazy Points: 2575 More actions · Answer 3

GilaMonster (3/12/2013)
aurato (3/12/2013)
Would you recommend migrating the databases on this disk to a different drive?
Well, ask yourself, would you leave important information on a drive that's giving repeated problems?

Migrating the database that was having issues tonight, but there are many production-critical databases on the suspect drive. We currently have a ticket open with the IO vendor. I'm not sure our team is treating this with enough urgency. No mention was made yet of migrating the other critical DBs (my reference to this thread has not fully convinced anyone that hardware is the issue). I will make the recommendation to move our most critical data to another drive.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 4

Yeah, most people aren't convinced until something fails catastrophically. Make sure your backups are good.

Also, it isn't necessarily the physical drive. Could be the firmware, drives, switch, cache, any filter drivers in the IO stack, etc. In short, anything between SQL and the physical disk platters. In most systems these days, that's a lot of parts.

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

aurato SSCrazy Points: 2575 More actions · Answer 5

GilaMonster (3/13/2013)
Yeah, most people aren't convinced until something fails catastrophically. Make sure your backups are good.
Also, it isn't necessarily the physical drive. Could be the firmware, drives, switch, cache, any filter drivers in the IO stack, etc. In short, anything between SQL and the physical disk platters. In most systems these days, that's a lot of parts.

The hardware support team concluded that because the temperature was unusually high on the drive (84 C), that was probably the cause. I'm told that we've installed some kind of extra cooling on it and now it's back within typical operational temperatures.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 6

That could well be it. Just keep an eye on things, run regular CheckDB and make sure that things remain OK.

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

aurato SSCrazy Points: 2575 More actions · Answer 7

GilaMonster (3/20/2013)
That could well be it. Just keep an eye on things, run regular CheckDB and make sure that things remain OK.

Thanks for all your help.