A database has presented the above errors. I have run DBCC CHECKDB, which r
evealed the affected table, then re-ran with REPAIR_REBUILD and the index co
rruption was corrected. Several days passed and the same errors appeared on
a different table. REPAIR
_REBUILD corrected the corruption again.
My questions:
What could be causing this?
Is it hardware related, like RAM or disk I/O?
Could it be application related?
How can I determine the cause and prevent future corruption?
Thanks a million!Yes, you very likely have a bad disk or IO controller. Data does not appear
to be written to the disks in a reliable fashion.
Make sure any SQL hardware is on the Windows hardware Compatibility List
(HCL). HCL certified gear with signed drivers should not exhibit this
behavior.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Tim Ermlich" <termlich(***take this out***)@.allenbrook.com> wrote in
message news:CAA5B69B-5B7C-43FF-834D-23546F0BE27F@.microsoft.com...
> A database has presented the above errors. I have run DBCC CHECKDB, which
revealed the affected table, then re-ran with REPAIR_REBUILD and the index
corruption was corrected. Several days passed and the same errors appeared
on a different table. REPAIR_REBUILD corrected the corruption again.
> My questions:
> What could be causing this?
> Is it hardware related, like RAM or disk I/O?
> Could it be application related?
> How can I determine the cause and prevent future corruption?
> Thanks a million!
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment