Cube "Process State" changing to UnProcessed


  • Hi

    Background: SQL 2008 SP1 Ent X64

    What is the criteria that determines when the Cube State is set to Unprocessed?  We are having problems where some cubes are suddenly changing their status to UnProcessed after a daily update (Update Dimensions with a process of just the latest partitions).

    We are also having problems during our weekly Full process of the cubes.  The standard procedure is to do a Full process of all the dims, then process all the measure group partitions.  We have this setup to minimize contention on the database to build as quickly as possible.  However, every now and then (no pattern that I can see), some of the cubes state will be set to unprocessed and the users then cannot use this cube.  We have to do a full cube process which can take a long time.

    One work around we have tried is to set the partitions to return no data (by changing the views the cube is based on) and then do a full cube process, then set the views back and process the measure groups.

    Anyone else had this issue and how did you get around it.
    Wednesday, January 20, 2010 11:28 AM

All replies

  • Just a suggestion as this used to happen to me on older version (2000) - if a full process of a dimension was required then this would make the cube un processed. Which processing oiption are you using for the dimension as one of the options will full process if it deems it necessary.


    Hope this helps (or gives you something to think about).


    Wednesday, January 20, 2010 11:47 AM
  • This happens occasionally when I do the daily update (using "Process Update") and occasionally on the weekly process ("Process Full").  For the weekly Process, it doesn't happen on all cubes, and not all the time.
    Wednesday, January 20, 2010 11:52 AM
  • Process Full on dims followed by proocess full cubes should leave you in a fully ok state with no issues. Sorry I cant help more I have yet to experience these problems with 2005 and 2008 probably I leant the painfull way with 2000.

    Check through the documentation. From memory the process update is the option that can trigger a full process. This is most likely the culprit.


    Wednesday, January 20, 2010 12:12 PM
  • Hi Michael,


    What is the issue you got? The user cannot browser the cube after finishing daily processing? And where did you check the cube state, in SSMS? Could you try to refresh the cube to check the state and last processed property again? Also, did you get any error message during processing? Process Default

    Detects the process state of an object, and performs processing necessary to deliver unprocessed or partially processed objects to a fully processed state.

    Sorry for so many questions.



    Friday, January 22, 2010 3:42 AM
  • Hi

    No problem.

    We have this problem intermittently.  The daily process does a Process Update of all Dimensions, then a full process of the relevant Measure group partitions.  When the users try to connect to the cubes, they do not display.  In SSMS, if you check the Cube properties, under status there is a State value.  This will be set to UnProcessed, even though all the measure groups are fully processed.  The only way I have found to fix this is to run a full process of the cube.  But that means reprocessing all measure groups, which can take a long time.

    I have some cubes where every day I do a Full Process on all Dimensions, then a Full process on each measure group (no process on the cube level) and these cubes remain in the Processed state all the time, never had a problem.

    So why would some cubes change their processed state, while others don't?

    Friday, January 22, 2010 5:26 PM
  • do you have linked measure groups in your cube?
    Friday, January 22, 2010 8:15 PM
  •   When the users try to connect to the cubes, they do not display.

    The partitions cannot be displayed or the dimensions cannot be displayed? Anyway, do a process default on a dimension will not cause cube/measures group/partitions become unavailable. I mean you can do process default on all dimensions and then you can still use the cube, and the cube’s state should be ‘processed’.

    But a process full on a dimension will cause cube/measures group/related partitions become unavailable/UnProcessed.


    Next time, before doing any process operation, remember to click the button ‘impact analyses’. It will list the objects and the state. For example, before click run button for process full, click button ‘impact analyses’, then you will see some object will the state ‘UnProcessed’, but no affected object by ‘process default’.


    More information about side effects by a processing, you can refer to;






    Monday, January 25, 2010 3:48 AM
  • Hi all,

    I'm having the same issue. Using Batch Processing Mode , rest of the cube is processed like dimension/measure group/partition but not the cube itself. The State of the Cube is still Unprocessed.


    Can't able to browse the cube. But if do another batch only for cube it works and it turn it process rest of my measure group/partitions etc.

    How to avoid this and make my cube state to processed. Any help and Suggesstions.


    Monday, July 12, 2010 5:54 AM