Timeline for maximum server memory setting in SQL Server [duplicate]
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 24, 2015 at 19:17 | comment | added | Razvan Zoitanu | Thank you, good read. Not using -g. x64 all the way, no AWE here. However, the issue was real, even if Task Manager might be wrong, memory was overused by that instance, as SSRS's logs showed a lot of reports were failing due to "System.OutOfMemoryException". | |
| Mar 24, 2015 at 19:15 | history | closed | Aaron Bertrand | Duplicate of SQL Server Max Memory not limiting use of RAM | |
| Mar 24, 2015 at 19:06 | comment | added | LowlyDBA - John M | First, @Shanky just posted a good writeup on not using Task Manager to monitor memory in SQL Server. You may see more memory used in 2012 since it has different memory configurations than previous versions - short version being you cannot explicitly limit all of the RAM it may consume. | |
| Mar 24, 2015 at 18:58 | history | asked | Razvan Zoitanu | CC BY-SA 3.0 |