﻿<?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 2008 / SQL Server 2008 Administration  / Dynamically managing SQL Memory / 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>Sun, 19 May 2013 03:55:30 GMT</lastBuildDate><ttl>20</ttl><item><title>Dynamically managing SQL Memory</title><link>http://www.sqlservercentral.com/Forums/Topic1385059-1550-1.aspx</link><description>Heres the scenario, I've recently come across involving a multi-instance SQL server server.The server itself hosts a multi tiered DW, with Staging, ODS and Warehouse located in their own instance of SQL server 2008.  However what happens is that Max Memory allocations are dynamically altered between each instances, depending on the state of the ETL process, so Staging-&amp;gt;ODS the memory will be configured to favour the ODS, then during ODS-&amp;gt;Warehouse load it will be switched to favour the Warehouse. The Actaul DB's (ODS and Warehouse) are Very large (1-2 TB each), and as far as I'm aware the server has a total of 512GB of physical ram.Is there a jusifitcation for doing this or would you be better leaving each instance with a fixed amount of memory?</description><pubDate>Thu, 15 Nov 2012 03:47:08 GMT</pubDate><dc:creator>Jason-299789</dc:creator></item></channel></rss>