When I read that best practices are to have the DB file on one drive (RAID5 for a lot of reads), the logs and the tempDB file and the backups on another drive (RAID1 for a lot of writes), this is confusing me and my network team. When you guys say separate out these files to different "disks" do you really mean "partitions"? Form what I am being told about RAID sets, that you can partition different drives to hold these files separately, but technically they are on the same disk. Is this still okay. For a dev environment, they are proposing the following solution, please le tme know if this follows best practices: Dev Server 1: 2 X 3.0 GHz 533 FSB 4GB RAM 10 Disk Drives in 3 RAID sets: 1st set: RAID1 Mirror 2 drives - 30GB - Holds OS and Page file 2nd set: RAID5 6 drives - 364GB usable - holds DB file, Backups, TempDB 3rd set: RAID1 Mirror 2 drives - 36.4GB - Holds the Logs Is it okay to have a HUGE RAID5 set and split out a few partitions, one partition having the DB, and the other partition having the TempDB and backup? Is this "Best practice"? Another thing that is very weird is that when I go into "Computer Mgmt." on my server it says I have 4 processors, however my network team says it really is only 2 physical processors. What is up with this? Apparently, to go to a 4 processor environment, the servers will not hold enough disks. Please advise. Thanks.