RAID10 Config query | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

RAID10 Config query

Hi there, I am at the point of creating the RAID10 array for the DB’s (the OS is already on RAID1), and for optimum performance I would like to know whether I should select one of the below settings above another, or just take the default settings? This is for a SQL 2000 server. STRIPE SIZE: 4 / 8 / 16 / 32 / 64K
READ POLICY: ADAPTIVE READ-AHEAD or READ-AHEAD
WRITE POLICY: WRITE BACK or WRITE THROUGH
CACHE POLICY: DIRECT I/O or CACHE I/O Thanks for the help in advance
This is probably a good start:http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops6.mspx You need to scroll down a bit. I think the second half of the article will be interesting.

Frank Kalis
Microsoft SQL Server MVP
http://www.insidesql.de
Ich unterstütze PASS Deutschland e.V. http://www.sqlpass.de)

this can also help
http://www.databasejournal.com/features/mssql/article.php/1460091 AKTHAR DILMOHAMUD
65 BENARES ST
PORT LOUIS
MAURITIUS
My [email protected]
Raid 5 will help you in that the INSERT / SELECT requests will now be spread over multiple hard drives. You pay a slight penalty in raid 5 for the parity information that protects you in case of a disk failure. You can avoid this penalty by going to raid 10 (raid 1 + raid 0). This is accomplished by mirroring two striped sets. Another good feature to get for raid is hot swappable hard drives. SQL Server will benefit from multiple processors and all the memory that you can throw at it. The ideal situation (if possible) is to have enough memory so that the entire database is memory resident. If data must be quickly recoverable, consider mirroring the transaction log and placing the database on a RAID 5 disk. RAID 5 provides redundancy of all data on the array, allowing a single disk to fail and be replaced in most cases without system downtime. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>