Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

The Voice of the DBA

Steve Jones is the editor of SQLServerCentral.com and visits a wide variety of data related topics in his daily editorial. Steve has spent years working as a DBA and general purpose Windows administrator, primarily working with SQL Server since it was ported from Sybase in 1990. You can follow Steve on Twitter at twitter.com/way0utwest

Warming up Analysis Services with Preallocate

With Windows Server 2003 many people found that Analysis Services (SSAS) was slow to get going sometimes. So a preallocate setting was introduced that allows you to specify the initial memory setting that SSAS will get when it starts. This setting is a percentage of the total memory, and you want to be sure this is set below your Low and Total memory limits. If not, the server will immediately start to clear things out of cache, or try to.

This is another entry in the XML configuration file for SSAS. It is set with the memory limits as follows:

<Memory>
<TotalMemoryLimit>80</TotalMemoryLimit>
<LowMemoryLimit>65</LowMemoryLimit>
<PreAllocate>50</PreAllocate>

Note that this doesn't make a different with Windows Server 2008. The OS is more efficient in allocating memory to SSAS immediately and using small allocations. There's a great blog post at MSDN that talks about this: Analysis Services Preallocate Memory Setting – Insight.



Comments

No comments.

Leave a Comment

Please register or log in to leave a comment.