Being careful in SSAS to not make a cube/dimension unprocessed

A big headache in SSAS, especially when dealing with a large cube, is making a change that when deployed, causes a cube to become unprocessed, forcing you to do a full process so the cube is usable.  Nothing is worse than making a change without realizing it will cause the need for a full process on all the partitions of a cube that will take many hours.

For example, a process full on a dimension will cause cube/measures group/related partitions to become unavailable/unprocessed.  Here are other actions that will make your cube unprocessed:

  • New measure group
  • New measure
  • Edit measure aggregation method
  • Edit dimension usage

Here are other actions that will make your dimension unprocessed (and therefore all cubes connected to the dimension become unprocessed):

  • Add an attribute to a dimension
  • Change the order by property of an attribute
  • Edit the attribute relationship
  • Add or delete dimension translation

So, make sure you understand which changes will cause an unprocessed state which makes the cube unusable so you can do it off-hours so you don’t end up getting angry phone calls that the cube is not working!

More info:

SSAS: Which change makes the cube/dimension unprocessed?

Processing Analysis Services Objects

Cube “Process State” changing to UnProcessed

About James Serra

James currently works for Microsoft specializing in big data and data warehousing using the Analytics Platform System (APS), a Massively Parallel Processing (MPP) architecture. Previously he was an independent consultant working as a Data Warehouse/Business Intelligence/MDM architect and developer, specializing in the Microsoft BI stack. He is a SQL Server MVP with over 25 years of IT experience.
This entry was posted in SQLServerPedia Syndication, SSAS. Bookmark the permalink.

One Response to Being careful in SSAS to not make a cube/dimension unprocessed

  1. Kiran says:

    Hi,
    Always i got stuck at an error when runnig job with cube.
    How can i trace the follwoing error, can any body suggest on this as urgent basis:

    “Unexpected end of file has occurred. The following elements are
    not closed: root, return, ExecuteResponse, soap:Body, soap:Envelope. Line 107952, position 1″

    thanks

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>