70-448 · Question #321
You are a database developer and you have about two years experience in creating business Intelligence (BI) by using SQL Server 2008. Now you are employed in a company named NaproStar which uses SQL…
The correct answer is C. You should set the AggregationUsage property appropriately. Review Aggregation Usage (Aggregation Design Wizard) SQL Server 2008 R2 Other Versions Use the Review Aggregation Usage page to configure aggregation usage settings. Options Default: Select to set the aggregation usage setting for the attribute to Default. By using this…
Question
You are a database developer and you have about two years experience in creating business Intelligence (BI) by using SQL Server 2008. Now you are employed in a company named NaproStar which uses SQL Server 2008. You work as the technical support. Now you receive an e-mail from your company CIO, in the e-mail, the CIO assigns a task to you. You use SQL Server 2008 Reporting Services (SSRS) to create a solution. The solution contains a dimension named DimDay and a measure group named FinishedSales. The DimDay dimension contains an attribute which is named Week. The FinishedSales references the DimDay dimension. According to the requirement of the company CIO, you must make sure that the aggregations designed on FinishedSales always include the Week attribute. So what action should be performed?
Options
- AYou should set the Usage property appropriately
- BYou should set the IsAggregatable property appropriately
- CYou should set the AggregationUsage property appropriately
- DYou should set the AttributeHierarchyEnabled property appropriately
How the community answered
(25 responses)- A8% (2)
- B4% (1)
- C76% (19)
- D12% (3)
Explanation
Review Aggregation Usage (Aggregation Design Wizard) SQL Server 2008 R2 Other Versions Use the Review Aggregation Usage page to configure aggregation usage settings. Options Default: Select to set the aggregation usage setting for the attribute to Default. By using this setting, the designer applies a default rule based on the type of attribute and dimension. Full: Select to set the aggregation usage setting for the attribute to Full. By using this setting, every aggregation for the cube must include this attribute or a related attribute that is lower in the attribute chain. The Full aggregation usage setting should be avoided when an attribute contains many members. If specified for multiple attributes or attributes that have many members, this setting might prevent aggregations from being designed because of excessive size. None: Select to set the aggregation usage setting for the attribute to None. By using this setting, no aggregation for the cube can include this attribute. Unrestricted: Select to set the aggregation usage setting for the attribute to Unrestricted. By using this setting, no restrictions are put on the aggregation designer; however, the attribute must still be evaluated to determine whether it is a valuable aggregation candidate. Set All to Default: Select to set the aggregation usage settings for all attributes to Default. The presence of an (All) level in an attribute hierarchy depends on the IsAggregatable property setting for the attribute and the presence of an (All) level in a user-defined hierarchy depends on the IsAggregatable property of the attribute at the top-most level of user-defined hierarchy. If the IsAggregatable property is set to True, an (All) level will exist. A hierarchy has no (All) level if the IsAggregatable property is set to False.
Topics
Community Discussion
No community discussion yet for this question.