Logan801 :
Thank you ferry much for your input buzznut. These are the wares that" have" to be on the system: server 2003 standard ( which means 32 bit) sql 32bit and the app that's going to be using them is a security app ie card access video recorder/server and there probably wouldn't be more than ten clients on it at once. Its the app that's ruining my plans for it to be a 64bit machiene. They always complain about how slow the server is that's why i was trying to go the 64 bit route. Will that combo above work for what i have described above?
Sorry about the slow response, I didn't get it til now. I think if you hit "Reply to buzznut" rather than quick reply, I'll get an email notification.
The combo you suggested will be quite a zippy machine. As I mentioned though, network throughput is going to be the main source of lag for your clients. Probably hard drive access would be next, which is why servers sometimes have raid drives to allow for speedy access (and redundancy of course, or I suppose that IS the primary reason for raid). In your case I wouldn't worry about that too much.
The main reason to go with a 64 bit machine is for the purpose of using more than 3 Gigabytes of memory (ram). It's not that 64 bit programs are damn fast, because they really aren't noticeably faster than 32 bit. But the 64 bit operating system is necessary for accessing more than 3 GB ram. This is useful in machines that carry out a lot of operations and for multitasking. Also good for folks who have SSD's, because instead of running a system cache on their hard drive and taking up precious real estate, they run without a cache and add more ram to ensure they never run out. Like about 8 GB usually.
I usually see lots of ram in webservers and other applications, but for your purposes 3 GB should be more than sufficient.
buzznut
Facebook
Twitter
Instagram