You are redesigning a SQL Server Analysis Services (SSAS) database that contains a cube
named Sales. Before the initial deployment of the cube, partition design was optimized for
processing time. The cube currently includes five partitions named FactSalesl through
FactSales5. Each partition contains from 1 million to 2 million rows.
The FactSales5 partition contains the current year’s information. The other partitions contain
information from prior years; one year per partition. Currently, no aggregations are defined
on the partitions.
You remove fact rows that are more than five years old from the fact table in the data source
and configure query logs on the SSAS server.
Several queries and reports are running very slowly.
You need to optimize the partition structure and design aggregations to improve query
performance and minimize administrative overhead.
What should you do? (More than one answer choice may achieve the goal. Select the BEST
answer.)
A.
Use the Aggregation Design Wizard to create aggregations for the current partitions.
B.
Combine all the partitions into a single partition. Use the Usage-Based Optimization
Wizard to create aggregations.
C.
Combine all the partitions into a single partition. Use the Aggregation Design Wizard to
create aggregations.
D.
Use the Usage-Based Optimization Wizard to create aggregations for the current
partitions.
difficult one, usage-based optimization and aggregation design wizard both are used to design aggregations. but optimization creates aggregations based on usage patterns or queries recorded in query log.
“After you use the Aggregation Design Wizard, you can use the Usage-Based Optimization Wizard to design aggregations based on the usage patterns of the business users and client applications that query the cube.”
https://msdn.microsoft.com/en-us/library/ms189706.aspx
https://msdn.microsoft.com/en-us/library/ms180144.aspx
I think D is ok
In question says “Several queries and reports are running very slowly” – so Usage-based Optimization i think is OK
D