BI Project note creation Time dimension (2)

Original: BI project note creation Time dimension (2)

To create a step:

Serial number	Selected properties	Renamed name	Property category
1	DateKey	DateKey	Conventional
2	Month Key	Month Key	Month
3	中文版 Month Name	中文版 Month Name	One month of the year
4	Month Number of year	Month Number of year	Conventional
5	Calendar Quarter Key	Calendar Quarter Key	Quarter
6	Calendar Quarter	Calendar Quarter	Conventional
7	Calendar year	Calendar year	Years

Now that we have established the time dimension, note that bids has produced a design warning, and we point the mouse at it, and we can see that the hierarchy was created in a non-parent-child dimension.



To adjust attribute relationships:

Adjust to:


View Dimdate Dimension Design warnings

Workaround:

Avoid using a property's Visible attribute hierarchy as a level in a user-defined hierarchy
http://technet.microsoft.com/zh-cn/library/bb630296 (v=sql.105). aspx

Tip: We can hide the attribute hierarchy so that he does not display it in the browser, but it is important to know that the structure of the attribute hierarchy is still there, which is why we should not ignore it when writing an MDX query, and we can get members from that hierarchy.

Follow the steps above to make the same changes to the calendar Quarter key and Month key properties.

Define attribute relationships as "rigid" in the appropriate location
http://technet.microsoft.com/zh-cn/library/bb630312 (v=sql.105). aspx

For best performance, you should typically set the RelationshipType property based on whether the relationship between the members changes over time:
For a relationship that you do not want to change, set the RelationshipType property to Rigid. A date in a given month is a relationship that does not want to change.
For the relationship that you want to change, set the RelationshipType property to flexible. Examples of relationships that may change over time have the marital status of the salesperson or customer within a given region.
Note: By default, the user interface always sets the RelationshipType property to flexible.
Setting the RelationshipType property determines whether analysis Services creates a rigid aggregate or a flexible aggregation. After an incremental update, Analysis Services removes the flex aggregations, so the aggregations must be manually re-processed, but Analysis Services retains the rigid aggregations.
RelationshipType
Indicates whether the member relationship changes over time. The values are Rigid and flexible, which indicate that relationships between members do not change over time, which indicates that relationships between members change over time. The default value is flexible. If you define a relationship as flexible (flexible), the aggregation is removed and recalculated as part of the incremental update (if only new members are added, the aggregations will not be removed). If you define a relationship as Rigid (rigid), analysis Services preserves aggregations when the dimension is incrementally updated. If a relationship that is defined as rigid has an actual change, analysis Services generates an error during the incremental process. Specifying the appropriate relationship and relationship properties can improve query and processing performance.

BI Project note creation Time dimension (2)