﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2005 / SQL Server 2005 Performance Tuning  / SQL Server Buffer Pool Management / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sat, 25 May 2013 11:07:08 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: SQL Server Buffer Pool Management</title><link>http://www.sqlservercentral.com/Forums/Topic911587-360-1.aspx</link><description>The buffer pool is basically all remaining memory. You can't really manage it at all beyond setting the min &amp; max values. Other than that, you manage how data is accessed, how the procedure cache is used, etc. Is there something specific you're looking for in this area or just general guidelines?</description><pubDate>Wed, 28 Apr 2010 06:26:12 GMT</pubDate><dc:creator>Grant Fritchey</dc:creator></item><item><title>SQL Server Buffer Pool Management</title><link>http://www.sqlservercentral.com/Forums/Topic911587-360-1.aspx</link><description>When SQL-Server request a data page it checks the in-memory   buffer cache before looking for the data page on the disk subsystem.   If the data page is found in the buffer pool, the processor will   retrieve the data and then perform the work required.   My question is what are some of the key factors I should   take into account to ensure I am setting the size of the buffer   pool? Ideal ways for buffer pool management?</description><pubDate>Tue, 27 Apr 2010 20:15:03 GMT</pubDate><dc:creator>JStevenson1</dc:creator></item></channel></rss>