Databases Reference
In-Depth Information
The Optimize for Adhoc Workloads option ensures that this scenario will never occur — and
because it only affects ad-hoc plans, we recommend switching it on by default in all installations of
SQL Server.
SUMMARY
In this chapter, you've learned the difference between physical and virtual memory and the limited
support SQL Server 2012 has for 32-bit environments.
You've also read about NUMA architectures and how SQL Server's memory model structures itself
around NUMA. And you've seen the Clerks and Caches that SQL Server uses, including the buffer
pool and the plan cache.
You've also learned about Workspace Memory, which supports hashing and sort operations; how to
determine an effective Max Server Memory setting; and that all of SQL Server's memory requests
are now governed by this setting.
Other coni guration settings you read about were Optimize for AdHoc Workloads, which prevents
cache bloat from single-use ad-hoc plans; and Lock Pages in Memory, which prevents Windows
trimming SQL Server's working set.
Search WWH ::
Custom Search