January 14, 2010 at 3:15 pm
I have an odd memory problem that I’ve not yet been able to figure out.
SSAS, peaks at 1.6 gig of memory, and wont use anything more. Even though there is 16 gig available, on the box.
Box specs
8 core 2.5g
16 gig ram
Windows Server 2003
Standard x64 edition
SQL Server Enterprise edition
Version 9.00.3353
Memory \ LowMemoryLimit = 75
Memory \ TotalMemoryLimit = 80
SSAS is running from the x64 directory ‘C:\Program Files\Microsoft SQL Server\MSSQL.2’
There is plenty of memory on this system and 80% of 2 gig of ram is 1.6 gig. However, there is no reason that SSAS should be capped at that little bit of memory. It should be consuming way more memory. Anyone got any pointers here?
May 13, 2010 at 10:15 am
Hi, i have the same problem.
How do you resolve?
May 13, 2010 at 12:29 pm
Well as it turns out, that process won't climb above the 1.6 mark, however, SSAS is indeed using all of the allocated memory. If you use the WMI to view memory usage it becomes clear that SSAS is indeed consuming that which what has been allocated to it.
Hope that helps
FYI, If your experiencing slow query times then odds are there are other issues at hand. For example, I found that my automated partition creation process had up and decided to move create a dimension on a different drive (my cubes are split against a few different drives). That one partition caused that cube to crawl to its knees, as more users dug for that data, it ended up bringing the entire server to a halt. Once I fixed it, all was okay in the world. (this was an issue that completely boggeled my mind...)
February 6, 2012 at 8:12 am
Stephan Douglas (5/13/2010)
Well as it turns out, that process won't climb above the 1.6 mark, however, SSAS is indeed using all of the allocated memory. If you use the WMI to view memory usage it becomes clear that SSAS is indeed consuming that which what has been allocated to it.
Hope that helps
FYI, If your experiencing slow query times then odds are there are other issues at hand. For example, I found that my automated partition creation process had up and decided to move create a dimension on a different drive (my cubes are split against a few different drives). That one partition caused that cube to crawl to its knees, as more users dug for that data, it ended up bringing the entire server to a halt. Once I fixed it, all was okay in the world. (this was an issue that completely boggeled my mind...)
Hi, where can I obtain the WMI script to view the memory usage to show how much SSAS is indeed consuming, please?
Thanks.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply