SQL Server Performance

OLAP cubes not processing

Discussion in 'Analysis Services/Data Warehousing' started by shill, Feb 16, 2005.

  1. shill New Member

    We have two OLAP cubes which have a full process carried out every night. The task is fired through a DTS package scheduled in the SQL Server Agent.

    This has been running successfully for a long time until recently, where the cubes are not being processed. There are no error messages in the Event Log, the task has a status of executing in the SQL Server Agent and there is no change in the modified date when I view the data files for the cubes.

    To work round the problem, I cancel the job, stop/start the OLAP service and then leave the processing until the following night or process one of the cubes which won't take as long to process. After doing a stop/start the task completes successfully again until the next time.

    Has anybody experienced something similar to this and what was the solution?
  2. Raulie New Member

    A shot in the dark.... is the cube processing after the loading has completed in your warehouse or fact table? I dont know your data loading schedules, but It could be that the data the cube is processing is yesterdays for example. Check that your source data is refreshed before processing.


    Raulie
    Hewlett-Packard
  3. satya Moderator

    And also could you plesae check SQLAgent log for this behaviour.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  4. Raulie New Member

    quote:Originally posted by shill

    the task has a status of executing in the SQL Server Agent and there is no change in the modified date when I view the data files for the cubes.

    If the status in SQL Agent is executing then the process is not being completed. A good idea is to set your DTS package to logging if you havent done so already. There you can also see how long the task is taking to run.

    If the processing time is taking much longer than usual then check other possibilities you most likely have a bottleneck somewhere.

    Raulie
    Hewlett-Packard

Share This Page