You are a database developer and you have about two years experience in creating
business Intelligence (BI) by using SQL Server2008.
Now you are employed in a companynamed NaproStar which uses SQL Server2008.
You work as the technical support. Now you are in charge of a SQL Server 2008 Analysis
Services (SSAS) database.
A Product dimension is contained in the database. The dimension contains two attributes
both of which have a Rigid relationship type.
The two attributes are the Category attribute and Subcategory attribute.
The relationship between the Category and Subcategory values is changed by the data
source for the Product dimension.
Now in order to make the dimension successfully reflect the change, you have to execute an
XML for Analysis (XMLA) command to process the dimension to perform this.
What action should you perform?

A.
In order to achieve this goal, the ProcessIndexes command should be used

B.
In order to achieve this goal, the ProcessAdd command should be used

C.
In order to achieve this goal, the ProcessClear and the ProcessDefault commands should
be used.

D.
In order to achieve this goal, the ProcessUpdate command should be used

Explanation:
ProcessFull ProcessFull applies to all objects. It discards the storage contents of the object
and and rebuilds them. ProcessFull is recursively applied to all descendants of the object as
well.
ProcessClear ProcessClear applies to all objects. It discards the storage contents of the
object.
ProcessClear is recursively applied to all descendants of the object as well.
ProcessDefault ProcessDefault applies to all objects. It does the bare minimum required to
bring the object to a fully processed state. In other words, it builds only the storage contents

that are not currently built. For example, if a partition has fact and aggregation data, then
ProcessDefault will only build the bitmap indexes. The only exception to the above rule is
bindings. When you change the bindings of an object (e.g., KeyColumns of a dimension
attribute), the object retains its data, but remembers that the bindings have changed.
ProcessDefault on the object will discard all the storage contents and rebuild them. The
server handles ProcessDefault by analyzing the object and dynamically converting it to
another processing option such as ProcessFull, ProcessIndexes, etc. ProcessDefault is
recursively applied to all descendants of the object as well. ProcessData applies only to the
OLAP objects, i.e. dimension, cube, measure group and partition. It discards the storage
contents of the object and rebuilds only the “data”. For dimensions, it builds only the attribute
and hierarchy stores. For partitions, it builds only the fact data. Essentially ProcessData
builds the bare minimum required for the object to be available for queries. Indexes are
considered optional and affect only the query performance. ProcessData is recursively
applied to all descendants of the object as well. ProcessIndexes applies only to the OLAP
objects, i.e., dimension, cube, measure group, and partition. It requires that the object must
already have its “data” built; otherwise, it raises an error. ProcessIndexes preserves the data
and rebuilds the “indexes”. For dimensions, it builds the bitmap indexes. For partitions, it
builds the aggregation data and bitmap indexes. ProcessIndexes is recursively applied to all
descendants of the object as well. ProcessUpdate applies only to dimensions. It is the
equivalent of incremental dimension processing in Analysis Services 2000. It sends SQL
queries to read the entire dimension table and applies the changes— member updates,
additions, deletions. Since ProcessUpdate reads the entire dimension table, it begs the
question, “How is it different from ProcessFull?” The difference is that ProcessUpdate does
not discard the dimension storage contents. It applies the changes in a “smart” manner that
preserves the fact data in dependent partitions. ProcessFull, on the other hand, does an
implicit ProcessClear on all dependent partitions. ProcessUpdate is inherently slower than
ProcessFull since it is doing additional work to apply the changes. Depending on the nature
of the changes in the dimension table, ProcessUpdate can affect dependent partitions. If
only new members were added, then the partitions are not affected. But if members were
deleted or if member relationships changed (e.g., a Customer moved from Redmond to
Seattle), then some of the aggregation data and bitmap indexes on the partitions are
dropped. The cube is still available for queries, albeit with lower performance. ProcessAdd
applies only to dimensions and partitions. ProcessAdd is a new processing option for
dimensions that did not exist in Analysis Services 2000. It essentially optimizes
ProcessUpdate for the scenario where only new members are added. ProcessAdd never
deletes or updates existing members. It only adds new members. The user can restrict the
dimension table so that ProcessAdd reads only the new rows. ProcessAdd for partitions is
the equivalent of incremental partition processing in Analysis Services 2000. The user
typically specifies an alternate fact table or a filter condition pointing to the new rows.
ProcessAdd internally creates a temporary partition, processes it with the specified fact data,
and merges it into the target partition. See the Out of Line Bindings section for details on
how to specify the new rows for ProcessAdd. ProcessStructure applies only to cubes and
mining structures. ProcessStructure for cubes is the equivalent of the Analysis Services
2000 processing option, processBuildStructure, in DSO. It discards the storage contents of
the cube and its partitions. It implicitly does a ProcessDefault on all dimensions of the cube
and marks the cube as processed. At this point, the cube is available to queries but it will not
return any fact data. This is supported mostly for backward-compatibility reasons. It was
useful in Analysis Services 2000 for parallel processing utilities. Once the “structure” of a
cube is processed, its partitions can be processed in parallel by multiple client sessions
without running into locking conflicts. ProcessStructure on a mining structure discards its
storage contents (training data) and rebuilds them. It does not affect the contents of the
mining models under the mining structure. ProcessScriptCache ProcessScriptCache applies
only to cubes. The MDX script in a cube can contain CACHE statements.
ProcessScriptCache evaluates the script and persists the results for the CACHE statements.
ProcessClearStructureOnly ProcessClearStructureOnly applies only mining structures. It
clears the storage contents (training data) of the mining structure while preserving the
contents of its mining models.