We have been given a new 64 bit SQL data warehouse server with 2008 enterprise installed. Here are the specs given to us by the server admin group:
*** Server Storage provisioning - two RAID-10 arrays have been configured with standby hot spares. Each array is one independent volume as follows D: 2.72TB E: 2.72TB
The OS Volume (C:) runs a RAID-1 Mirror - total space of 465GB – with 428GB currently free ***
We have to migrate about 15 user databases from our current data warehouse to the new server and I'm trying to figure out the best way to configure the data and log files. I was thinking of separating out the data files to D: and log files to E:, but not sure if having just the log files on E: is overkill.
I was also thinking of moving tempdb over to the D: and tempdb log over to E: to take advantage of the RAID 10, but not sure if it is a good idea to have tempdb on same drive as data files.
Separating log files is definitely not an overkill.Make sure that you benchmark the disk for sequential I/O's.How many spindles do you have for the drive you want to put the log file on ?If you have multiple then that is surely an overkill as you will be wasting it on sequential I/O's.
Don't understand the idea of having RAID for tempdb.Rather Data files and sql binaries should be going for RAID 1+0.
After Monday and Tuesday even the calendar says W T F ....
No do not treat tempdb as a system database.treat it as another user database.Have it on a faster separate disk.I would suggest go for RAID 0 for tempdb as it will benefit from striping and of course multiple file groups to prevent allocation contentions for tempdb.
Between any idea of how many physical disks there are ?
After Monday and Tuesday even the calendar says W T F ....
SQL 2008 SAN configurations
Posted - 05/07/2012 : 11:15:13
