...but the SSAS 2005 server is running on a machine with a 12 Gig page file.
Although it is a big select statement (with "intersect()"s and "hierarchize()"s and multiple cross-joins), I would expect the query to complete successfully. If there is a shortage of memory, I would think the server would simply make use of the paging file (all 12 Gig).
The machine is an HP dual-IA64 server with 4 Gig of RAM running W2K3 SP1. The SSAS 2005 instance has been upgraded to SP1 recently.
Any ideas?
Thanks!
Which flavour of Analysis Services 2005 are you using?
We've also had problems with memory usage - typically, though, when processing the dimensions or measure groups. Is the machine dedicated to SSAS, or does it have e.g. SQL Server installed as well?
Regards,
Will.
|||Hi, Hippunky! Thanks for replying.
The machine has both IIS and the full "suite" of SQL Server services installed (Sql Server, SSAS, SSIS, RS, SQL Agent, etc.) The SSAS installation is the full (mostly default) install.
Bob
|||I've bumped the paging file to 30 Gig (24 Gig wasn't enough), and the MDX query starts successfully (before it was failing almost immediately with the "paging file too small" message). I'll post if it completes successfully.
"Just talking to myself...",
Bob Hodgman
|||
Hmmm... I didn't mark this as the answer although it certainly took care of the initial failure. So I guess it is the "answer" to that issue.
However, the query has been running for 22 hours and 53 minutes, so far.
TGIF.
Bob
|||We've been having the same problem when we process our dimensions and cube. How did you change the size of the paging file?
TIA
No comments:
Post a Comment