- {2003, 2008},
- {64, 32}
Its stage webserver with mssql
Tell me more
×
Server Fault is a question and answer site for
professional system and network administrators. It's 100% free, no registration required.
|
|
|||||||||||||
|
|
Assuming this isn't a performance sensitive role, 2008 x86 will run just fine on 512MB of ram for basic core services like DC, DNS, File/Print and so on in a limited scope. Especially a 2008 Core will do wonders down to 256MB of memory actually. 64bit version will tend to draw a bit more so 2008 R2 isn't perfect for this constraint - but not impossible. I'd heavily recommend against 2003 as you want to run an up-to-date operating system no matter the platform to prevent stability, vulnerability and support issues. 2000 and earlier should not even be considered. Getting MSSQL to run on top of this, especially with an application server like IIS, will be more of a problem though - but that certainly won't change with an older version of Windows Server. |
|||
|
|
|
2003 without a doubt. Earlier versions of Windows (NT4, 2000) will certainly run better, but in practical terms you might have trouble getting apps (like a version of MSSQL) that are supported on them. Security-wise 2003 will also be more robust against newer threats than NT4 or 2000 can ever be these days. With that amount of memory (any specific reason why you can't upgrade it to a gig or 2?) 32 bit is the way to go - there is no real advantage to the larger address space of 64 bit here, and in fact 64 bit will consume quite a lot more RAM and push you to the limit sooner. |
|||
|
|
