black_b[ ]x
[H]ard|Gawd
- Joined
- Jul 1, 2002
- Messages
- 1,753
My understanding of SQL server is that it's supposed to suck up as much memory as it can, then give it back to the OS as needed, but that this might be slow to react.
It's currently using almost 1GB (according to task manager) on a server with 4GB of physical RAM. We only have one database, max of 3 simultaneous users (typically just 1), and the database size (through SQL management studio) is 100MB with ~50MB "space available." The database will not grow very fast.
Can I set the max memory for the server to 256MB or 512? Any thoughts on a safe range? It's also a file server for our network, running exchange 2003, symantec mail security and symantec endpoint protection for 7 clients. I'm about to put Windows Search on it too so we can index some network folders.
It's currently using almost 1GB (according to task manager) on a server with 4GB of physical RAM. We only have one database, max of 3 simultaneous users (typically just 1), and the database size (through SQL management studio) is 100MB with ~50MB "space available." The database will not grow very fast.
Can I set the max memory for the server to 256MB or 512? Any thoughts on a safe range? It's also a file server for our network, running exchange 2003, symantec mail security and symantec endpoint protection for 7 clients. I'm about to put Windows Search on it too so we can index some network folders.