I've seen SQL server file corruption in a several case (handful) in the past 12 years or so. But as the article states it is 99.9% hardware related and I can concur with that statement.
Most of the time I see it on servers that are 8-10+ years old and the drive controller is going out and/or drives are becoming faulty and people don't bother setting up raid controller failure alerts.
This is really a by product of having critical mass (millions of installations) and poor hardware management. It's our fault (humans) for not paying attention.
From: Roger Harman [mailto:roger_harman@xxxxxxxxxxx]
Sent: Tuesday, January 29, 2013 3:02 PM
To: 'Midrange Systems Technical Discussion'
Subject: How the SQL Server World Lives
One of the newsletters I subscribe to is http://www.sqlservercentral.com
A recent article, "My SQL Server Database is Corrupt - Now What?!", had some interesting statements from the author:
. I was asked how often corruption really occurs in the real world.
My answer was, "hundreds to thousands of times every week across the world, in the tens of millions of SQL Server databases.".
. Every single week I receive multiple emails asking for some advice
about corruption recovery. When I'm teaching about corruption in our High Availability and Disaster Recovery Immersion Event, I always tell the class that I expect every DBA to see database corruption at some point during their career.
. I'll end by saying this: if you think that corruption won't happen
to you at some point in your career, I think you'll be surprised. Be prepared!
I'm curious.. How many of you have seen corruption on our platform? In 25+ years on S/38, AS/400, and IBM-i, I have NEVER had an issue with corrupt files/tables. In 1 year of SQL Server at my former employer, I saw it happen at least 3 times. I was shocked but the Microsoft bigots in the company just shook it off as status quo.
Here's the article but you have to be a member to read it.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l