Mistake: letting SQL Server keep its default memory limit. The buffer pool caches data and index pages, and SQL Server can otherwise allocate as much memory as it needs for that cache. section 10.3
That choice can starve Windows and required agents such as antivirus, monitoring, or inventory tools. The risk increases when Lock Pages In Memory prevents the working set from being trimmed. section 10.3 section 10.14
A 64 GB server
For a solitary SQL Server instance on a 64 GB server, a 48 GB maximum buffer-pool allocation leaves approximately 25% for Windows and other requirements. Multiple instances require that allowance to be divided between them. section 10.3
Listing 10.3 Configuring maximum memory
sp_configure 'show advanced options', 1 ; RECONFIGURE ; GO sp_configure 'max server memory', 49152 ; RECONFIGURE ; GO
Use sp_configure to enable advanced options and set max server memory; the value is specified in megabytes. section 10.3
Safer practice:
- Configure max server memory instead of accepting the default. section 10.3
- Reserve memory for Windows, other applications, and SQL Server components outside the buffer pool. section 10.3
- Recalculate the allocation when hosting multiple SQL Server instances. section 10.3
