Hello all,Any help with this is appreciated. I have very little experience with SSAS so any info suggestions are good. Also If you need any more info let me know.I will explain the the xmla Query, machine setup, then the cube setup and then the steps I have taken to try and solve the problem.[size="6"][b]The XMLA Query:[/b][/size]I have an xmla query which when run consistently fails after about 5 runs.[code="xml"]<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine"> <Parallel maxParallel="4"> <Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2"> <Object> <DatabaseID>CUBENAME</DatabaseID> <CubeID>CUBENAME</CubeID> <MeasureGroupID>V Fact Answer</MeasureGroupID> <PartitionID>FactAnswer_2001</PartitionID> </Object> <Type>ProcessIndexes</Type> <WriteBackTableCreation>UseExisting</WriteBackTableCreation> </Process> <!-- ....... There are about 180 ProcessesIndexes followed by about 5 ProcessFulls. --> <Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2"> <Object> <DatabaseID>CUBENAME</DatabaseID> <CubeID>CUBENAME</CubeID> <MeasureGroupID>V Fact Calculated Benchmark Questionnaire Group Gaps</MeasureGroupID> <PartitionID>V Fact Calculated Benchmark Questionnaire Group Gaps</PartitionID> </Object> <Type>ProcessFull</Type> <WriteBackTableCreation>UseExisting</WriteBackTableCreation> </Process></Parrallel></Batch>[/code]The XMLA query takes about 10 seconds to run. Then inexplicably it stops running.The Last 2 Messages I see are:[b]Finished processing the 'FactMetadataAnswer_2003' partition.Finished processing the 'Metadata Answer' measure group.[/b]The query does not timeout. Does not respond to cancel command. The only solution is to restart the machine. We have this problem in on several test environments at the moment.[b][size="6"]Machine Setup[/size][/b]The machine is Windows 2008, 8.00GB RAM, 64 bit, Dual Processors (2.53 GHZ) each.SQL Server is installed on the same machine.[b][size="6"]Cube Details[/size][/b]In the cube we have 17 dimensions. 18 Measure Groups. Each measure Group is partitioned by year since 2001. So in total there are about 240 partitions across all the measure groups.[size="6"][b]Steps to Solve the Problem[/b][/size]1. Because SQL Server is installed on the same machine I have restricted both SSAS and SQL Server to only use a maximum of 40% of the memory. Initially SQL Server was setup to use all available memory and SSAS around 80%.2. The CommitTimeout was set to zero. Thinking that the commit was taking forever I set this value to 30000 (5 minutes). This had no affect.3. ThreadPool \ Process \ MaxThreads - Increased from 64 to 150. No affect.Next I started analysing the Performance Counters:One strange thing I have noticed:1. All values for MSAS 2008: Cache stay at zero. I don't know what this means. Anyone know if this is bad?For these errors I have logged all the MSAS performance counters and I have the flight recorder switched on. I can provide lots more info if needed. I am really just looking for suggestions as for things to do, things to check, etc.Cheers,Padraic
↧