LearnPerformance
SQL Server Memory: Are Your Settings Right?
1 min readUpdated 6 Nov 2026
SQL Server is designed to use the memory you give it, so 'memory is 90% used' is rarely the problem. The problem is when the operating system or another process has nothing left.
Max server memory is the setting that matters
By default SQL Server will keep taking memory until it is nearly gone. Set a maximum that leaves room for the operating system, the backup agent, monitoring tools, and anything else installed on the machine. Then watch the server instead of the tool.
- Windows 'available megabytes of memory' warnings are the clearest sign the limit is too high.
- Repeated restarts of the service or a machine that swaps are the second sign.
- If other tools live on the box, budget their memory before setting the SQL limit.
Read pressure, not usage
The useful question is whether the buffer pool is big enough for the data you read every day. Two signals answer it:
- PAGEIOLATCH_SH waits rising means data is coming off disk more often than it should.
- A page life expectancy that keeps collapsing means the cache is being pushed out.
What not to chase
Do not chase a number. A server sitting at 95% memory usage with no I/O waits and a stable page life expectancy is healthy. A server at 70% with constant read waits is not — memory is only the symptom you can see.
Change max server memory in one place, on purpose, and record it. Ad-hoc memory changes are one of the most common unlogged overnight changes.
What to remember
- Set max server memory so the operating system keeps room.
- Judge memory by read waits and cache pressure, not usage.
- High usage with no waits is healthy.
- Record every memory change like any other change.
