Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

RAID Expand / Collapse
Author
Message
Posted Wednesday, October 28, 2009 7:51 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 5:50 PM
Points: 7,923, Visits: 9,649
I knew what the answer would be, so I got it "right". But "right" has to be in quotes, because it is actually wrong for application screnarios where disk utilisation is high - - the fact is that if decent disc performance is required then RAID 5 provides no protection against single disc failure, for two reasons: (i) during disc recovery the RAID's performance will not be adequate to support your workload, and (ii) disc recovery takes far longer than for RAID 10 and any disc failure during that recovery is a catastrophic failure (while for RAID 10 during recovery there is only 1 disc whose failure would be catastrophic). Every DBA who is involved in making storgae decisions should read and fully understand the material at http://www.baarf.com.
Or for a view from a RAID manufacturer who decided that RAID5 was no longer worth supporting see
http://et.aset.psu.edu/working_notes/storage/iSCSI/docs/Intransa_RAID_White_paper.pdf.

That paper from Intransa was 6 years ago! And the way disc drive technology is changing - drive storage capacity going up much faster than disc throughput - the performance and security hits against raid 5 are getting bigger every year while the cost savings of raid 5 against raid 10 are getting less every year.

RAID 5 is OK if your database has a very low write rate and you can accept a disc read throughput reduction by a factor of 4 or more (depending on number of spindles in the set) during disc recovery; it's useless otherwise. It's good for holding read-only tables, provided the read rate is low enough. It's almost always bad news for transaction logs, for tables that are frequently updated, for tables that grow rapidly, and for applications very high disc throughput.


Tom
Post #809939
Posted Saturday, October 2, 2010 9:21 PM


Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Tuesday, October 14, 2014 11:01 AM
Points: 703, Visits: 327
http://en.wikipedia.org/wiki/RAID
Raid 1 requires a minimum of 2 disks and protects against n-1 disk failures, not a 'single' disk failure, although it would protect against any 'single' disk failure even in it's minimum configuration. Raid 5 is the only selection available that never protects against more than a 'single' disk failure. More guessing games to try to figure out the author's meaning. Some authors are just being straightforward like this one and some seem to try to trick you with semantics.
Post #997263
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse