Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Dynamically managing SQL Memory Expand / Collapse
Author
Message
Posted Thursday, November 15, 2012 3:47 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, July 18, 2014 9:09 AM
Points: 870, Visits: 2,385
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->ODS the memory will be configured to favour the ODS, then during ODS->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?


_________________________________________________________________________
SSC Guide to Posting and Best Practices
Post #1385059
Posted Wednesday, January 29, 2014 4:39 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, March 12, 2014 4:23 AM
Points: 22, Visits: 95
I'm doing the same although for my application I give the database 59GB out of 64GB for the ETL and then trim it down to 12GB to free up the rest for processing an analysis services cube.

It seems to work but are there downsides? And no, we can't ask for more memory at this stage. We only just got it bumped up from 32GB six weeks ago.

I am considering the same method as the original post just for the last part of the ETL as well, since that is very memory-intensive and would utilise as much as we can throw at it. Trouble is by the time the ETL gets to the last step SQL has already taken a lot of the memory available to it.
Post #1535828
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse