We have 10 gigs of RAM for a server and are putting MSAS and SQL Server on
the same server (no choice for that for now). We are using the /3G switch to
allow 3 gigs for MSAS and the /PAE switch for enabling AWE.

The goal is for MSAS to use the first three Gigs of RAM, the OS to use the
next one, and SQL Server to use the next 6 for a total of 10 gigs.

THe problem is that when you engage awe, SQL Server takes the first 6 it can
get. So, we have to get MSAS up to 3 gigs of RAM and then turn on SQL
Server. I have a query script that will take MSAS up to 3 gigs over 45
minutes, but this is not 'elegant' nor quick.

Does anyone have any ideas on how to make SQL Server take its Gigs of RAM
starting after 4?

Or, barring that, does anyone have any better ideas to get MSAS to grab all
three gigs of ram in a few seconds?

Thanks,

Chris

No replies ...

So, I wrote a small C++ app that takes up 3 gigs.

The process right now is:

I run the C++ app and it reserves 3 gigs.
I start SQL Server with AWE - so it uses gigs 5-10 (6 gigs)
I turn off the C++ app, releasing the first 3 gigs.
Then I start MSAS, giving it the first three gigs, even if it doesn't take
them yet.

Thanks,

Chris

ps. (if we need to, this can be automated, for example, to run after an
unexpected server restart, but for now, we've left it manual)



"Chris" wrote:

Memory allocation with SSAS doesn't work like that. When you set the high
and low memory thresholds, it doesn't allocate memory in the conventional
sense of how the RDBMS goes out and physically grabs memory. They are just
numbers which the runtime engine examines when it allocates virtual address
space (malloc). If the total memory allocated (virtual address space -- not
physical memory -- remember that NT is a 32-bit virtual memory OS) crosses
the threshold, then the runtime system starts to do something. There is a
chapter dedicated to this topic in the SSAS Operations Guide at:
http://www.microsoft.com/technet/pro.../anservog.mspx
see the topc titled: "Memory" in the Configuration Management section.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Chris" <Chris (AT) discussions (DOT) microsoft.com> wrote