Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mikebird
Aged Yak Warrior
529 Posts |
 Posted - 2010-05-21 : 06:04:46
|
| I need to set plans for a new SQL Server 2005 machine with a 3.2Gb HR database to manage, which will expand at a rate I have no way to tell. I can't see the user activity via a current server hosted by a 3rd-party development company. I expect it to be the most stagnant DB I'll see. A web server looks after viewing data and requesting changes.When moving the system in-house, if I start with 1Gb memory, and a 10Gb hard disk, would this be viable, and just adding resources which may be needed, or not ever? We have this these resources on a virtual PC here at the moment. No plomblems |
|
|
mikebird
Aged Yak Warrior
529 Posts |
Posted - 2010-05-21 : 07:24:06
|
| Sorry if this is boring. I've used busy 24Gb clustered financial servers, with more RAM than the database size, and many others - telcos... Not much going on with HR. Sometimes I'm lost on tiny databases with hardly any activity. What about running it all on a really old laptop in the corner, bought from eBay, with 512Mb memory? |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-05-21 : 10:40:30
|
I can't see it running "good enough to use" on less than 1GB of RAM - we tend to install as-much-RAM-as-database-size or some multiple thereof too ... but for DEV databases we have massive databases running on shared servers with pitiful amounts of RAM, but then they only get accessed in fits & starts, and us DEVs don't care too much on performance - we connect to small test datasets when doing normal work / testing.Are you sure HR are only going to look at this APP when the Moon is Blue?  |
|
|
|
|
|
|
Server Config