Pulling It All Together
Thus far, we've explored the individual components of SQL Server's memory architecture in some detail. In this section, we'll pull these elements together so you can better understand how SQL Server manages memory overall and why it behaves the way it does in certain circumstances.
When you start SQL Server, the BPool's upper limit is computed based on the physical memory in the machine, the max server memory sp_configure value, and the size of the MemToLeave region. Once this size is computed, the MemToLeave region is set aside (reserved) so that it will not be fragmented by the BPool reservations that are to follow. The BPool region is then set aside, using as many as 32 separate reservations in order to allocate around ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access