I'm looking for guidelines for sizing the SQL box (SQL2005) which will be the logging database for an EE array (ISA2006).
Am looking at ~9000 user community (mostly students), with a view to replacing the ISA2000 proxy initially, and subsequently adding capabilities and leveraging the awesome power of an ISA box. Firewalling as a next step is a definate, as is OWA and RPC/HTTP publishing in addition to all websites being published through it.
Can't find anything that I can really hang my hat on (hence the ping), but am leaning towards the following
worst case, I'll over-engineer and go for: AMD Proc 8 GB RAM Raid 0+1 divided into 4 - C: = OS + ISA Binaries, - E: = Page File - F: = SQL Transation Logs - G: = SQL Database Gigabit NIC, x2
I *KNOW* I won't go down in flames with this config, but it is over-engineered and overly cautious; my preference would be to put something into place that reflects a bit more thought, style and panache (i.e. actually fits and is a very good use of available $'s, rather than the 'everything but the kitchen sink' approach).
The SQL sizing info on the MS site is horribly out of date.
Hi Pat, Key things are covered here. Max out the proc, memory and NIC speed (gigabit NIC will help a lot).
Also, SQL logs grow very quickly. For that number of users, make sure you have at least 500GB free for the DB, and more is better. Even then, you'll need to run SQL pruning scripts to wipe out the dead space and bring them down to size on the weekends.