Mercutio
Fatwah on Western Digital
Here's what I'm dealing with:
One of my coworkers has developed an application that relies on MSSQL + IIS (and it's an asp .net thing, so it's going to stay on IIS) that targets a specific market, which is health care related.
The offices I've visited in attempting to sell this setup don't have dedicated data closets or even much soundproofing. And, because this stuff is medical in nature, the people we're selling to actually want this system in-house.
This system in part automates a lot of paper workflow into .pdfs. We're not sure about long-term storage requirements.
So I need a server system with decent-ish expansion that's also exceptionally quiet. I take this to mean that actual "server" parts are out. No redundant PSUs or 15krpm fans.
My starting point will probably be some kind of i5-based machine, 4GB RAM, 2x250GB drives for OS (SBS 2003 or 2008; I need MSSQL, IIS and Sharepoint to implement everything), and at least 2TB additional internal storage, preferably in a form that supports online expansion. I'll probably add one or two 2TB USB3 drives to cover backup needs. I'm also going to make sure each customer gets a nice, big UPS.
I'm looking at a Silverstone HTPC case and a 500W Seasonic PSU. The case is a bit of a sore spot. I could go with a generic rackmount enclosure but none of these customers have racks. These machines will at best be sitting on a shelf in a regular closet. Very possibly the one where employees are hanging up their coats.
Because I won't be able to use "real" server hardware, I'm planning to purchase an extra motherboard, two spare hard drives and a power supply to leave on-site for the customers; these people seem to be really interested in having full ownership of the systems.
My proof of concept machine is a 4GB Q6600, which is why I think 4GB is plenty of RAM and an i5 is likely enough CPU for the application. In all honesty, I could probably get away with an i3.
I'm still trying to decide if I want to build these systems on top of VMware. I think it makes some sense to do things that way, but I'm getting the impression that doing so is going to confuse anyone else involved in the maintenance of these systems. I'm not sure I'll be around here forever; setting it up now might make it easier to migrate that system later and it might confuse the hell out of another tech brought in to work on it.
One of my coworkers has developed an application that relies on MSSQL + IIS (and it's an asp .net thing, so it's going to stay on IIS) that targets a specific market, which is health care related.
The offices I've visited in attempting to sell this setup don't have dedicated data closets or even much soundproofing. And, because this stuff is medical in nature, the people we're selling to actually want this system in-house.
This system in part automates a lot of paper workflow into .pdfs. We're not sure about long-term storage requirements.
So I need a server system with decent-ish expansion that's also exceptionally quiet. I take this to mean that actual "server" parts are out. No redundant PSUs or 15krpm fans.
My starting point will probably be some kind of i5-based machine, 4GB RAM, 2x250GB drives for OS (SBS 2003 or 2008; I need MSSQL, IIS and Sharepoint to implement everything), and at least 2TB additional internal storage, preferably in a form that supports online expansion. I'll probably add one or two 2TB USB3 drives to cover backup needs. I'm also going to make sure each customer gets a nice, big UPS.
I'm looking at a Silverstone HTPC case and a 500W Seasonic PSU. The case is a bit of a sore spot. I could go with a generic rackmount enclosure but none of these customers have racks. These machines will at best be sitting on a shelf in a regular closet. Very possibly the one where employees are hanging up their coats.
Because I won't be able to use "real" server hardware, I'm planning to purchase an extra motherboard, two spare hard drives and a power supply to leave on-site for the customers; these people seem to be really interested in having full ownership of the systems.
My proof of concept machine is a 4GB Q6600, which is why I think 4GB is plenty of RAM and an i5 is likely enough CPU for the application. In all honesty, I could probably get away with an i3.
I'm still trying to decide if I want to build these systems on top of VMware. I think it makes some sense to do things that way, but I'm getting the impression that doing so is going to confuse anyone else involved in the maintenance of these systems. I'm not sure I'll be around here forever; setting it up now might make it easier to migrate that system later and it might confuse the hell out of another tech brought in to work on it.