<Insert Picture Here> Optimizing ASO

Transcription

1

2 <Insert Picture Here> Optimizing ASO Steve Liebermensch Consulting Technical Director

3 The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle s products remains at the sole discretion of Oracle.

4 Agenda Dimension settings and usage Compression Accounts Time MDX optimization Materialization Data load

5 Dimension Settings and Usage Compression Compression dimension is not mandatory, but helps performance The compression dimension is a dynamic dimension Should be the column headers in a data load file Ideal compression is achieved if the leaf level member count is evenly divisible by 16

6 Dimension Settings and Usage Accounts Dynamic dimension Allows for non additive unary operators Required for time balance functionality Expense flags are accomplished through UDAs and member formulae In the case of large GL type accounts dimensions should consider storing the dimension

7 Dimension Settings and Usage Accounts Must be a dynamic dimension due to - unary operator

8 Dimension Settings and Usage Accounts Simplest hierarchy and allows for maximum stored aggregates. Leverages load rule setting of sign flip on UDA. Requires the user to accept different signage of values.

9 Dimension Settings and Usage Accounts Preserves original signage and allows for some aggregates to be stored

10 Dimension Settings and Usage Time Can make a good candidate for compression dimension Should be stored Use multi-hierarchy dimension if formulae are necessary To-date formulae Prior to best if performed in Time dimension and forward, best to use analytic dimension

11 Dimension Settings and Usage Time Use analytic dimension if you need perform time calculations like period to date sums, period over period comparisons Use AGGREGATE function if your period to date calculations need to take Time Balance tags into account ORACLE CONFIDENTIAL

12 Agenda Dimension settings and usage MDX optimization Data vs. meta data Eliminate unnecessary functions Simplify syntax NonEmpty directive Materialization Data load

13 MDX Optimization Meta-data vs data Performance difference between the following statements: IIf(Scenario.CurrentMember = Actual,.) Or IIf(Is(Scenario.CurrentMember,Actual),.)

14 MDX Optimization Goal is to calculate a products 3 month average Transactions contribution % to total 3 month average Transactions:

15 MDX Optimization Round( ( ( ([Time].CurrentMember,[Products].CurrentMember,[Transactions]) + ([Time].CurrentMember.Lag(1),[Products].CurrentMember,[Transactions]) + ([Time].CurrentMember.Lag(2),[Products].CurrentMember,[Transactions]) ) / (([Time].CurrentMember,Ancestor (Products.CurrentMember, Products.Generations(2)),[Transactions]) + ([Time].CurrentMember.Lag(1),Ancestor (Products.CurrentMember, Products.Generations(2)),[Transactions]) + ([Time].CurrentMember.Lag(2),Ancestor (Products.CurrentMember, Products.Generations(2)),[Transactions]) ) ),4)

16 MDX Optimization Round( ( ( ([Time].CurrentMember,[Products].CurrentMember,[Transactions]) + ([Time].CurrentMember.Lag(1),[Products].CurrentMember,[Transactions]) + ([Time].CurrentMember.Lag(2),[Products].CurrentMember,[Transactions]) Remove unnecessary ) / functions. Formatting (([Time].CurrentMember,Ancestor should (Products.CurrentMember, left to the Products.Generations(2)),[Transactions]) reporting tool. + ([Time].CurrentMember.Lag(1),Ancestor (Products.CurrentMember, Products.Generations(2)),[Transactions]) + ([Time].CurrentMember.Lag(2),Ancestor (Products.CurrentMember, Products.Generations(2)),[Transactions]) ) ),4)

17 MDX Optimization ( ( ([Time].CurrentMember,[Products].CurrentMember,[Transactions]) + ([Time].CurrentMember.Lag(1),[Products].CurrentMember,[Transactions]) + ([Time].CurrentMember.Lag(2),[Products].CurrentMember,[Transactions]) ) / (([Time].CurrentMember,Ancestor (Products.CurrentMember, Products.Generations(2)),[Transactions]) + ([Time].CurrentMember.Lag(1),Ancestor (Products.CurrentMember, Products.Generations(2)),[Transactions]) + ([Time].CurrentMember.Lag(2),Ancestor (Products.CurrentMember, Products.Generations(2)),[Transactions]) ) ) Avoid unnecessary references to CurrentMember. It is assumed without explicitly using a function

18 MDX Optimization ( ( ([Time].CurrentMember,[Transactions]) + ([Time].CurrentMember.Lag(1),[Transactions]) + ([Time].CurrentMember.Lag(2), [Transactions]) ) / (([Time].CurrentMember,Ancestor (Products.CurrentMember, Products.Generations(2)),[Transactions]) + ([Time].CurrentMember.Lag(1),Ancestor (Products.CurrentMember, Simplify formulae, no need to Products.Generations(2)),[Transactions]) use 5 functions + where 1 will ([Time].CurrentMember.Lag(2),Ancestor do. 3 CurrentMember (Products.CurrentMember, functions and 2 Lag Products.Generations(2)),[Transactions]) ) functions )

19 MDX Optimization Sum(LastPeriods(3),Transactions)/ Sum(LastPeriods(3), (Ancestor (Products.CurrentMember, Products.Generations(2)), Transactions)) Don t use a function where direct referencing can be performed. In this model Gen 2 of the Products dimension will always be the same member

20 MDX Optimization Sum(LastPeriods(3),Transactions)/ Sum(LastPeriods(3),([All Merchandise], Transactions))

21 MDX Optimization Only perform calculation when data to support the math exists Case When Not IsEmpty(Sum(LastPeriods(3),Transactions)) Then Sum(LastPeriods(3),Transactions)/ Sum(LastPeriods(3), ([All Merchandise],Transactions)) End

22 MDX Optimization Additionally you should break up the complex formula using an additional member: Create a new member [Last 3 Month Transactions] Assign the formula: NonEmpty directive, Sum(LastPeriods(3),Transactions) coming in Then the new % Contribution formula becomes: NonEmptyMember [Last 3 Month Transactions] Sum(LastPeriods(3),Transactions)/ Sum(LastPeriods(3),([All Merchandise],Transactions))

23 Agenda Dimension settings and usage MDX optimization Materialization Query Hints Default Query Tracking Size Choose your own adventure/have it your way materialization Data load

24 Materiaization Query Hints Default Query Tracking Size Choose your own adventure/have it your way materialization

25 Materialization Query hints On Dimension/Hierarchy

26 Materialization Query hints Dimensional intersections

27 Materialization Default In Analytic Administration Services Through Maxl execute aggregate process on database database name ;

28 Materialization Query tracking based In Analytic Administration Services Through Maxl alter database database name enable query_tracking; MDX report definition; execute aggregate process on database database name based on query_data; alter database database name disable query_tracking;

29 Materialization Results of aggregate selection Default selection 26 views Hierarchy option 24 views Dimensional Intersection 24 views Query Tracking 2 view No views were shared amongst all 4 aggregate selection processes Only 2 views were shared between more than 2 selection processes 7 views were shared in total

30 Materialization Database size In Analytic Administration Services Through Maxl execute aggregate process on database database name stopping when total_size exceeds size factor ;

31 Materialization Number of views In Analytic Administration Services Through Maxl execute aggregate selection on database database name selecting number of views views;

32 Materialization By default Aggregate Storage Option is parallel threaded with two threads, can use up to 8 When loading incremental data, aggregate views are also updated Materialization scripts can be saved and reused to eliminate regeneration of query tracked results The database can be available during materialization without data consistency issues

33 Agenda Dimension settings and usage MDX optimization Materialization Data load Behavior Slice loading Optimization

34 Data Load Behavior Within a buffer duplicate records are additive irrelevant of load rule settings When committing the buffer it adheres to data load rule setting related to overwrite, add to, or subtract from Single threaded, can use DLTHREADS cfg settings but thorough testing should be performed Materialized views are updated as part of the data load process during an incremental update

35 Data Load Slice loading Is the primary feature enabling Excel based lock and send and trickle feeding functionality Creates subcubes alongside the primary slice of the database Dynamic aggregations are performed across the necessary slices to provide query results Different materialized views might exist within a slice as compared to the primary slice of the database

36 Data Load Optimization Compression dimension should be across the load file Consider removing aggregate views prior to an incremental update of data Data should be loaded as additive values Multiple buffers can be used to parallel load the database. Requires simultaneous Maxl processes to be executed Ignore Zeros and Missing values whenever possible, buffer setting

37 Questions????? <Insert Picture Here>