I have a cube that has been running fine for over a year. Now when the full
process runs it just never ends. Also A.S. has become increasingly less
stable. The stop and start of the service takes awhile.

Does any one have suggestions as to why the service and cube are dieing? I
have reapplied SP3a and rebooted but am still having the same problems.

If you have had significant growth in the number of dimension members or
dimensions or databases, then it may be that you are running out of memory.
Do service restart on MSSQLServerOLAPService (the Analysis Services service
name). After it stabilizes but before users start doing anything on the
system, compare the virtual memory used by the msmdsrv process with your
Minimum Allocated (aka Low Memory) and Memory Consurvation Thresholds (aka
High Memory). The delta between your stabilized virtual memory and High
Memory is

For more information on how memory is allocated and used, see the following
two white papers:
http://www.microsoft.com/technet/pro.../anservog.mspx
http://www.microsoft.com/technet/pro.../ansvcspg.mspx

And before you ask -- yes, the above is right. Indeed we have two names for
exactl y the same thing.

The runtime engine is msmdsrv.exe. Thus its process name is msmdsrv. It is
also registered as an NT service and the service's name is
MSSQLServerOLAPService. So you look for "msmdsrv" in one place and
"MSSQLServerOLAPService" in another -- when they both are referring to the
same thing. Go figure. :-)

Hope this helps.
--
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.

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

Thanks for the information Dave. I will need to do further research and
consider your comments. My quick fix was to trim off two years of data. So
that leads me to believe that it is a memory issue.

"Dave Wickert [MSFT]" wrote:

Hello Mike,
i had same issues while a go and solved it
by migrating the AS repository to SQL Server.
The AS repository is default an Access db.

HTH
Jörg


"Mike Mullane" wrote: