Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We're setting up a SQL2008 system with the following virtual disks (not including the OS/Apps volume):

RAID10 Data
RAID1 Logs

Any recommendations as to how we should setup the RAID controller cache settings for each of these three VDs? The options are:

Write: write-back(WB) / write through(WT)
Read: read ahead(RA) / adaptive read ahead(ARA) / No Read ahead(NRA)

The RAID controller (512MB cache) has a battery backup unit.

share|improve this question
Why RAID 1 for TempDB? If you're allocating a RAID volume to it, you want it to be fast... but you shouldn't care about losing it, since it's only used for temporary operations. That's one of the few cases where RAID 0 would make sense. – Massimo Jun 21 '10 at 22:22

Definitely use write cache for transaction logs; they're always written and almost never read.

And, if they get actually read, this is done sequentially, so a read cache would be completely pointless.

share|improve this answer

I'd say.

Logs: NRA & WB
Database: (ARA or NRA) & WB
tempdb: (ARA or NRA) & WB
share|improve this answer

I'd be tempted to switch off write caching altogether but use 100% of your cache for ARA - but then again I'm quite paranoid about transactional integrity and don't fully trust BBWC - you may have more faith.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.