SG0-001 · Question #256
A customer has a database server that processes a great deal of data very quickly. They have identified a bottleneck in the storage subsystem and requested a change to the RAID configuration. How woul
The correct answer is B. Stripe across 15K rpm drives D. RAID 1+0. For a high-performance database server with a storage bottleneck, the optimal RAID configuration is RAID 1+0, utilizing 15,000 RPM drives for superior I/O performance and data protection.
Question
A customer has a database server that processes a great deal of data very quickly. They have identified a bottleneck in the storage subsystem and requested a change to the RAID configuration. How would you configure the new RAID group? (Choose two.)
Options
- AStripe across 7200 rpm drives
- BStripe across 15K rpm drives
- CRAID 6
- DRAID 1+0
- ERAID 5
How the community answered
(44 responses)- A27% (12)
- B57% (25)
- C5% (2)
- E11% (5)
Why each option
For a high-performance database server with a storage bottleneck, the optimal RAID configuration is RAID 1+0, utilizing 15,000 RPM drives for superior I/O performance and data protection.
7200 RPM drives are slower than 15K RPM drives and would likely worsen or at least not alleviate a storage bottleneck in a high-performance database environment due to their higher latency and lower throughput.
15,000 RPM (15K RPM) drives offer significantly faster rotational speed and lower latency compared to 7200 RPM drives, which is crucial for database servers that perform many random read/write operations and require quick access to data.
RAID 6 provides strong data protection with two parity blocks, but its write performance is generally lower than RAID 1+0 due to the overhead of calculating and writing two parity blocks for every write operation, making it less suitable for high-write database workloads.
RAID 1+0 (or RAID 10) combines mirroring (RAID 1) for high data protection and striping (RAID 0) for performance. This configuration provides excellent random I/O performance and strong fault tolerance, making it ideal for I/O-intensive applications like databases that demand both speed and resilience.
RAID 5 offers good read performance and reasonable data protection but suffers from poor write performance, especially during rebuilds, due to single parity. For a high-performance database with many write operations, RAID 5 would likely exacerbate the bottleneck.
Concept tested: RAID levels and drive types for database performance
Source: https://learn.microsoft.com/en-us/previous-versions/sql/sql-server-2008-r2/dd758806(v=sql.105)?redirectedfrom=MSDN
Topics
Community Discussion
No community discussion yet for this question.