You can cut the cost by using SATA but you cut performance and reliability as well so it's not really worth it unless it's a backup or archival near-line server.

It sounds like you only need single CPU and 6 72GB 15K SCSI disks in a DL380G4 with write cache enabler is probably what you want but maybe a bit pricey once you add redundant fans and CPU. You can mix RAID 5 and RAID 10 on the same disks but with todays size of disks it isn't really necessary any more, RAID 10 set using all 6 disks for the OS with write cache off with about 20GB and the rest also in RAID10 for data/logs with write cache on ought to be fairly good performance. SQL doesn't use the page file which is why I would have 2 logical disks to avoid wasting write cache on the system disk.

Thx - the DL380 is a great box but yes pricey - any reasonable alternatives?

Could you please explain the raid config a little more - correct me pls but wouldn't raid 10 give me 2x 72 GB as my storage space? Then the prob is that if I go to 120GB disks I've got to buy 6 of them?

And (groan) I've got a 3rd party vendor that says that all us network guys are just SCSI happy and he's using SATA servers all over the place. Any links to ammunition?

I would look to memory as a definite addon to speed up SQL pre-fetch caching. Also, RAID1 is fast and resilient, or RAID10 for more disks. However, I would probably look to use RAID5 on 3 76GB drives, RAID1 on pair of 76GB drive for OS and binaries. This leaves a floating Hot Spare for both arrays. This will give you 150GB useable. If this is not enough either up the disk size to 143GB or 300GB drives.

On a single CPU, 4GB RAM DL380 G4 you would be advised to limit your disk space in SQL to around 300GB max anyway. Allocate SQL to as much memory as possible to maximise the caching capabilities of SQL. Also, use lots of transaction logging on a sperate disk if possible. An alternative configuration would be
3 x RAID1 pairs.
1 for OS and Binaries
1 for Data
1 for Log files & SQL Dumps

This would make the OLAP speeds much faster as the disks are not contending for anything.

Minimum RAM = 4GB. Controller needs pre-fetch caching battery backup. This would make for a disk I/O performance based system.

SCSI is faster, SATA is cheaper but slower. As you state I/O performance is a key, stick with SCSI. However there are SATA with NCQ drives that are coming up to spec wrt outright disk speeds. SCSI uses a lot less CPU cycles so I would still stick with this, especially on a SQL server.

Cooling is nowhere near as good as that found in the TX300, though. There's only a pair of active processor heatsinks, a fan in the power supply and a large variable-speed fan at the rear of the chassis. None of the fans are truly hot-swappable, and the hard disk and expansion bays have no accompanying fans or any facilities to fit one to them.

Furthermore, it was disconcerting to hear the main chassis fan constantly varying its speed, indicating that either its sensor was too sensitive or it was having trouble holding a stable internal temperature.

Are these dealbreakers? What is people's experience of this box?

Whew end of Q - if I have any more I'll post another Q with title:
small biz server + backup recommendations2 Thanks again

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled

This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…

This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites.
Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…