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 |
|
dmeagor
Starting Member
16 Posts |
 Posted - 2012-03-13 : 20:32:42
|
| I've explicitly set the Maximum Memory value in SQL server 2008R2 to 13000MB but when I check the task manager I see it is using 14,071,448KB (13,741MB)The reason I'm concerned is because we set the maximum value because the server crashed recently due to a low memory condition where SQL server had allocated almost all of the server memory.I've checked and the number I have entered is correct (i.e not entered in kb by mistake)Any ideas?David Meagor |
|
|
Sachin.Nand
2937 Posts |
Posted - 2012-03-15 : 06:45:08
|
| SQL Server is in serious need of memory.You need to urgently increase the RAM in your SQL box.After Monday and Tuesday even the calendar says W T F .... |
 |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2012-03-15 : 09:46:43
|
| Max server memory sets the size of the buffer pool. There is some memory taken outside of the buffer pool for things like thread stacks, CLR, backup buffers and a few other things. It's ususally not a lot of memory.Reduce the max server memory a little (maybe by 500 MB), that should get the memory allocated back into the range you want.Note that this is not a sign of memory pressure, it's normal behaviour.--Gail ShawSQL Server MVP |
|
|
|
|
|
|
Maximum memory setting not working