I am running SQL2005 EE/Win2003 64bit. I have jobs that process data into the SSAS db/ cubes. Periodically the jobs just hang (without loading data) and I am unable to connect to SSAS using SS Mangement Studio & Profiler etc. I can find no errors or diagnostics or predict if/when it will happen again.
If I restart the SSAS service, everything works - till the next time.
Has anyone experienced / overcome a similar problem please ?
Seems like the old problem of SQL Server 2005 SSAS with multi-processor machines. The default settings are fine for most SQL Server 2005 Analysis Services installations because the Memory Quota Manager will limit the number of parallel operations based on available memory. However, on high end servers with large amounts of RAM available the Memory Quota Manager is likely to allow a much higher number of parallel operations to occur, resulting in the number of process or query threads quickly exceeding the default thread pool sizes. The delay encountered for each thread created above the thread pool size can quickly accumulate and give the appearance that processing has slowed or completely stalled. Please follow this link to sort out if this is the problem.
3 People are following this question.
