Professional Documents
Culture Documents
Contents.
Aggregate Concepts. Building Aggregates. Performance Analysis Tools & Techniques. Aggregate Maintenance.
Aggregate Concepts:
Definition: Aggregates are materialized subsets of Info cube data, where the data is preaggregated and stored in an Info cube structure Purpose: To accelerate the response time of Queries, by reducing amount of data that must be read in the database for a navigation step.
OLAP Processor
4
Aggregates can be created : For Basic Info Cubes. On dimensional Characteristics. On Navigational attributes. On Hierarchy levels. Using Time dependent navigational attributes. Using Hierarchy levels where the structure is Time-dependent.(>=3.x)
Multi provider
Remote cube ODS object Info set
Sales Data
Customer
Win soft Inter N/w Funny duds Inter N/w Thor Ind. Funny duds Win soft
Aggregate Country
Country
USA Germany Austria
Sales Data *
Sales 40 35 20
Sales
10 15 5 10 10 20 25
Sales Data
Sales 10 15 5 10 10 20 25
Aggregate
Sales Data
Customer Win soft Inter N/w Funny duds Inter N/w Thor Ind. Funny duds Win soft
Country Customer
F Germany *
Sales 15 20
Info cube
Country
USA Germany USA Austria Austria Germany USA
Sales Data
Customer
Win soft Inter N/w Funny duds Inter N/w Thor Ind. Funny duds Win soft
Aggregate
Sales Data
Sales
10 15 5 10 10 20 25
Customer-Industry *
CustomerIndustry Technology Consumer Prod Chemical Sales
60
25 10
Country
Valid from Sales person
Info cube
Country
USA Germany USA Austria Austria Germany USA
Sales Data
Customer
Win soft Inter N/w Funny duds Inter N/w Thor Ind. Funny duds Win soft
Sales
10 15 5 10 10 20 25
Europe
America
Germany
Austria
USA
Info cube
Country
USA Germany USA Austria Austria Germany USA
Sales Data
Customer
Win soft Inter N/w Funny duds Inter N/w Thor Ind. Funny duds Win soft
Sales
10 15 5 10 10 20 25
Aggregate
Sales Data
Country H, Level 2 *
Country America Europe Sales 40 55
As many queries are comprised of multiple select statements, they may be automatically split up over several aggregates.
Query
DB Access
DB Access
DB Access
Aggr1
Aggr2
Info Cube
After the split, OLAP processor searches for an optimal aggregate for each part. Parts which use the same aggregate will be combined again (in some cases it is not possible to combine them).
Relatively small compared to parent Info Cube Try for summarization ratios of 10 or higher Find good subsets of data (frequently accessed) Build on some hierarchy levels, not all Not too specific, not too general should serve many different query navigations Should be frequently used and used recently (except basis aggregates)
Exceptions: A large aggregate containing navigational attributes may benefit Performance despite its size (but remember the tradeoff) Basis Aggregate may be large and may not be used for reporting but still be useful for maintenance
Save status Filled Aggregation level (Type of aggregation like..* , F ,H) * => based on char value. F => fixed value is the type of aggregation H => Hierarchy level Records=> no.of records in aggregate. Records summarized ( mean value)=> no.of rec in infocube/no.of rec in aggr. (i.e.,average no.of records in info cube that are combined to form a record in the aggregate). Valuation ---I , I+,I++++,I etc It is systems estimate Of aggregate value .(depending on the usefulness of the aggregate) Usage=> no.of times that aggr has been accessed by olap processor for reporting. Last used => Indicates when the aggregate is last used. Fixed Hierarchy Hierarchy level 0factcount value for each rec in aggr=> no.of rec in infocube that were aggregated for that char combination.
Proposal by Combination.
ST03 (Workload Monitor) RSRT (Query Monitor) RSDDSTAT Table. RSRTRACE (Trace Tool) RSRCATTTRACE.
RSRTQuery Monitor
RSRTQuery Monitor
RSRTRACETrace Tool.
RSRTRACE->RSRCATTTRACE
Aggregate Maintenance
Aggregate maintenance is required to:
Achieve the balance between : Time to maintain aggregates and Many Fast Queries. See that the data in aggregate must be in sync with the underlying Info cube. See that the changes in Hierarchy/attributes should be available to the aggregate.
Maintenance of Aggregates
Activating & Filling: To use an aggregate when executing a query you should first activate it and then fill it with data. Roll Up: To apply newly loaded Transactional data to the aggregate. Change run: To activate the changes of master data and hierarchies. During Change run, all aggregates containing navigational attributes and/or hierarchies are realigned Adjustment of time dependent aggregates: To recalculate aggregates with time dependent navigational attributes.
Thank You!!!