You need to minimize the amount of time required to process the cube

HOTSPOT
You are designing a dimension named Employee for a SQL Server Analysis Services
multidimensional project.
The Employee dimension contains a DateOfBirth attribute and a MaritalStatus attribute.
You need to minimize the amount of time required to process the cube.
What should you do? To answer, select the appropriate relationship type for each attribute in
the answer area.

HOTSPOT
You are designing a dimension named Employee for a SQL Server Analysis Services
multidimensional project.
The Employee dimension contains a DateOfBirth attribute and a MaritalStatus attribute.
You need to minimize the amount of time required to process the cube.
What should you do? To answer, select the appropriate relationship type for each attribute in
the answer area.

Answer:

Show Hint

Leave a Reply 3

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

Monik

Monik

Rigid Relationship: This relationship should be defined when you are sure that members will not change over time. For example, time dimension relationships should almost always be defined as rigid. Each month in a calendar hierarchy (January 2012) will always be associated with a defined year (2012) so the relationship will always be a rigid one. Rigid relationships do not require re-computation during incremental processing which reduces overall processing time.

Flexible Relationship: The flexible relationship should be defined when you know that there is a possibility of a dimension attribute changing over time. For example, a person’s address or phone number can change from time to time so these relationships should be defined as flexible. On the server side in a flexible relationship, Analysis Services is forced to drop and re-compute any existing aggregations which will add a bit of processing time.

Reply