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 |
|
aiken
Aged Yak Warrior
525 Posts |
 Posted - 2002-07-18 : 16:07:40
|
| I've got a SQL server running on a box with 1GB of memory. SQL's memory configuration is set to Dynamic, with a minium of 0 and maximum of 1023. However, I just noticed that even after being up for a few days, SQL Server is only usign 450MB. There's about 400MB free on the server right now.The highest usage database on the server is about 9GB, so I know that memory could be used for caching. Do I just need to crank up that minimum value to 750MB or so? Is there some reason why SQL Server decided not to use all available memory (there are no other apps or services running on the box, other than NT itself and the bare minimum in services).Thanks!-Brooks |
|
|
aiken
Aged Yak Warrior
525 Posts |
Posted - 2002-07-18 : 16:13:12
|
| Ok, I was/am confused. I think I misintrepreted some perfmon stats, but I still don't get what's going on.Here's the data:Server memory: 1GBCommitted Bytes: ~ 480MBAvailable Bytes: ~ 450MBSQLServer Private Bytes: ~1GBSQLServer Virtual Bytes: ~1.2GB...I guess I'm just confused about the difference between private bytes and committed bytes. I was under the impression that they both represented physical memory, but apparently not.So which is it? Why does the server think it has 450MB of available bytes?Thanks-b |
 |
|
|
|
|
|
SQL Server not using all memory?